linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Ian Molton <spyro@f2s.com>, Anton Vorontsov <cbou@mail.ru>,
	Matt Reimer <mreimer@vpop.net>
Subject: Re: [PATCH 1/3] pda-power: add set_charged functionaltity
Date: Mon, 20 Jul 2009 20:37:11 +0200	[thread overview]
Message-ID: <20090720183711.GF19257@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090720182752.GA20602@oksana.dev.rtsoft.ru>

On Mon, Jul 20, 2009 at 10:27:52PM +0400, Anton Vorontsov wrote:
> On Thu, Jul 16, 2009 at 05:44:02PM +0200, Daniel Mack wrote:
> > This adds a function to let the power supply core know that the battery
> > is fully charged now. This can be done by watching a GPIO line, for
> > example.
> > 
> > Some battery drivers might need that information to calibrate
> > themselves.
> > 
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > Cc: Ian Molton <spyro@f2s.com>
> > Cc: Anton Vorontsov <cbou@mail.ru>
> > Cc: Matt Reimer <mreimer@vpop.net>
> > ---
> >  drivers/power/power_supply_core.c |   16 ++++++++++++++++
> >  include/linux/power_supply.h      |    3 +++
> 
> The patch is missing pda_power.c part?

Erm, does it? What would you expect it to do in there?

> >  #if defined(CONFIG_POWER_SUPPLY) || defined(CONFIG_POWER_SUPPLY_MODULE)
> >  extern int power_supply_is_system_supplied(void);
> > +extern void power_supply_set_battery_charged(void);
> 
> I don't quite like this interface. Note that system might want
> to know if it's supplied (hence global is_system_supplied(void) call),
> but having set_battery_charged(void) interface makes little sense
> (well, it makes sense for small embedded systems that have just
> one battery and one charger)...
> 
> There is a supplied_to psy field that might help you there...

Hmm. I thought about that too, but didn't find a way to access the
single members of the pda-power device and find the right one to
access. They're registered on a string base and matched magically once
the battery monitor is probed when found on the one-wire bus. Any
proposal how an interface could look like that does that?

All I need is a way to pass this information from my platform code down
to the battery driver.

> The cleanup patch looks OK though, I'll apply it.

Thanks. What about the one adding support for the bootstrapping of the
current_accum value? I've sent that inline as a reply to the other patch
series (4/4) last week (which was probably not a good idea).

Daniel


  reply	other threads:[~2009-07-20 18:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 15:44 [PATCH 1/3] pda-power: add set_charged functionaltity Daniel Mack
2009-07-16 15:44 ` [PATCH 2/3] pda-power: EXPORT_SYMBOL cleanups Daniel Mack
2009-07-16 15:44   ` [PATCH 3/3] ds2760: implement set_charged() feature Daniel Mack
2009-07-16 16:08     ` Daniel Mack
2009-07-20 12:24 ` [PATCH 1/3] pda-power: add set_charged functionaltity Daniel Mack
2009-07-20 17:53 ` Matt Reimer
2009-07-20 18:27 ` Anton Vorontsov
2009-07-20 18:37   ` Daniel Mack [this message]
2009-07-20 19:00     ` Anton Vorontsov
2009-07-20 21:00       ` Daniel Mack
2009-07-22 17:20       ` Daniel Mack
2009-07-22 17:41         ` Anton Vorontsov
2009-07-23 18:34           ` Daniel Mack
2009-07-23 18:35             ` [PATCH 1/2] power_supply: get_by_name and set_charged functionality Daniel Mack
2009-07-23 18:35               ` [PATCH 2/2] ds2760: implement set_charged() feature Daniel Mack
2009-07-28 22:06               ` [PATCH 1/2] power_supply: get_by_name and set_charged functionality Daniel Mack
2009-07-29 10:29                 ` Ian molton
2009-07-29 10:36                   ` Daniel Mack
2009-07-29 12:45                     ` Ian Molton
2009-07-30 14:11                       ` Anton Vorontsov
2009-07-30 17:41                         ` Daniel Mack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090720183711.GF19257@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=cbou@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mreimer@vpop.net \
    --cc=spyro@f2s.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).