On Sat, 7 Nov 2009 23:43:11 +0200
Ilya Petrov <[email protected]> wrote:

> 2009/11/5 Antonio Ospite <[email protected]>:
>
> > Even if battery status is always unknown it looks like it still reports
> > voltage and temperature. Is voltage_now the current charge _level_?
> 
> its unknown, because of missing eoc_regulator.
> yep, voltage_now is charge_level.
> 
> btw, native ezx software used some calibration data from bp to convert voltage
> into charge percents.
>

If you know some details about this, please post them here.

> > Is there a way to read the _instant_ power consumption?  I mean, in
> > order to see if there is some power leakage, or to compare power
> > consumption with some subsystem powered on or off.
> 
> yep. there is adc channel for this.
> look at res[1] in pcap_show_adc_battcurr() from old ezx-pcap [0]
>

Ok, thanks

> >BTW, what about splitting pcap_battery and eoc_battery (or eoc_charger)?
> 
> maby its good, but i dunno, how to make cross-references in two modules :)
> 
> charger should know battery level and battery should know charger state.
>

I see, if it was easy I think you would have developed two separate
drivers in the first place.

> 
> [0] 
> http://git.openezx.org/openezx.git?a=blob;f=drivers/mfd/ezx-pcap.c;h=836a9ed0cc9024e96fb16ff09772b0845afbc411;hb=f284d7d4a5ab75fb012ebd1274d8a9fa27aec171
> 
> 
> btw, can you fix tg branch ezx/eoc_charger. looks like i missed
> something this time.
> i created it as child of ezx/eoc but it didnt apper in ezx/current
> after tg update
>

Just tell me what you want me to do. Just a child branch of ezx/eoc?

master <-- ezx/eoc_charger <-- ezx/eoc

right?


Regards,
   Antonio

-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Attachment: pgpRFZfhKbD02.pgp
Description: PGP signature

Reply via email to