* Arthur D. <spinal.by@xxxxxxxxx> [200315 20:51]: > Now about the chosen limits. For some reason the charging is > interrupted (and restarted after a while) when the following > conditions are met: > 1) the charging current is < 112 mA > 2) the display backlight is off > > This behaviour was observed in Maemo Leste with hildon-desktop > running. I tested these patches for several days, so I picked up > the parameters for optimal (from my point of view) work in practice > taking into account the current "features" of Droid 4 drivers. > > If we could somehow fix this behaviour (charging interruption), > I'd reconsider the end of charge current value to be 50 mA. Hmm well we do have two chargers, the usb charger and the unknown inductive charger for the pins on the back. It would be best to keep cpcap-battery.c independent of the chargers to avoid depndencies as the chargers do usually start charging briefly always when connected. Maybe just adding something like below would be enough of a check: static int cpcap_battery_get_counter_rate(struct cpcap_battery_ddata *ddata, int poll_time_ms); And then based on the value being negative or positive you would know if it's charging or not. I guess we could then use this also for POWER_SUPPLY_PROP_CHARGE_NOW with poll_time_ms value of 0. I think the charge counter is configure to poll at 250 ms right now. Regards, Tony
