On Mon, Sep 27, 2010 at 3:35 PM, Arun Murthy <arunrmurthy.83@xxxxxxxxx> wrote: > On Mon, Sep 27, 2010 at 4:24 PM, Grazvydas Ignotas <notasas@xxxxxxxxx> wrote: >> On Mon, Sep 27, 2010 at 10:21 AM, Arun Murthy <arunrmurthy.83@xxxxxxxxx> wrote: >> The problem is that BCI is only active while charging, when it is not >> charging most (all?) monitoring registers freeze and no monitoring >> happens (BCI registers read frozen values from last charge). So I >> don't register battery as it has no useful data to report. I heard it >> is possible to use MADC to perform monitoring while not charging, so >> battery can be added when MADC driver is merged and corresponding code >> is written for this driver. >> > How do I check the battery voltage? > I need to check the battery voltage/current/temp and, if I am not > wrong these are obtained from MADC. > MADC driver has to be added first and then the battery. > With being able to read the basic parameter battery voltage, this > driver becomes incomplete. Incomplete driver is better than no driver, don't you think? There are some boards like pandora or oswald that have additional battery monitoring chips (as twl monitoring is pretty crude anyway), those boards would have fully functional charging now. Currently mainline kernel is not very useful with them simply because the battery runs flat. > How do I get notified if battery voltage is low and needs charging > from user space? Either additional monitoring chip notifies you (if you are lucky and have one), or wait for update of this driver :) There are efforts to merge MADC driver [1], but it may take some time. [1] http://marc.info/?t=128461535700002&r=1&w=2 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
