From: Pavel Machek <pavel@ucw.cz>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Mike Rapoport <mike@compulab.co.il>,
linux-kernel@vger.kernel.org
Subject: Re: Smart Battery System Design (was: Re: Question about userspace-consumer)
Date: Fri, 14 Aug 2009 18:32:01 +0200 [thread overview]
Message-ID: <20090814163201.GB1626@ucw.cz> (raw)
In-Reply-To: <20090811223645.GA4691@sirena.org.uk>
Hi!
> > and wrt SBS, that would mean basically writing a driver for that Smart
> > Batery Charger and the Smart Battery devices creating means for some
> > entity to tell _start_charging_ based on the presence of a power source.
>
> For me the critical thing is that we ensure that the charger won't be
> left charging at anything more than a trickle charge when there's
> nothing monitoring the battery status. If the charger can do the SBS
> charger stuff autononmously it can look after itself (but the use of the
> regulator API becomes more questionable for those devices since the
> charger will be doing all the management of the regulators). If the SBS
> is done entirely in software the kernel at least needs to be able to
> notice the management software exiting and clean up after it, even if
> that's all it is able to do for itself.
Please don't put basic fastcharge logic to userspace:
* you still want to fastcharge at init=/bin/bash boot
* you want to fastcharge while machine is in s2ram. See spitz. Doing
that with userspace would be quite tricky.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-08-15 16:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 20:05 Question about userspace-consumer Felipe Balbi
2009-08-10 21:58 ` Mark Brown
2009-08-11 5:44 ` Felipe Balbi
2009-08-11 9:40 ` Mark Brown
2009-08-11 10:30 ` Liam Girdwood
2009-08-11 20:49 ` Smart Battery System Design (was: Re: Question about userspace-consumer) Felipe Balbi
2009-08-11 20:59 ` Felipe Balbi
2009-08-11 22:36 ` Mark Brown
2009-08-12 6:47 ` Felipe Balbi
2009-08-12 10:05 ` Mark Brown
2009-08-12 19:07 ` Felipe Balbi
2009-08-12 22:53 ` Mark Brown
2009-08-14 16:32 ` Pavel Machek [this message]
2009-08-15 16:43 ` Mark Brown
2009-08-15 22:34 ` Pavel Machek
2009-08-16 9:18 ` Mark Brown
2009-08-22 9:28 ` Pavel Machek
2009-08-22 10:16 ` Mark Brown
2009-08-21 14:01 ` Pavel Machek
2009-08-22 14:16 ` Mark Brown
2009-08-22 19:35 ` Pavel Machek
2009-08-23 9:08 ` Mark Brown
2009-08-11 12:09 ` Question about userspace-consumer Mike Rapoport
2009-08-11 12:56 ` Mark Brown
2009-08-11 20:40 ` Felipe Balbi
2009-08-14 16:31 ` Pavel Machek
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=20090814163201.GB1626@ucw.cz \
--to=pavel@ucw.cz \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=me@felipebalbi.com \
--cc=mike@compulab.co.il \
/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
all inboxes | Powered by JetHome®