[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090822101641.GC4344@sirena.org.uk>
Date: Sat, 22 Aug 2009 11:16:42 +0100
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Pavel Machek <pavel@....cz>
Cc: Felipe Balbi <me@...ipebalbi.com>,
Liam Girdwood <lrg@...mlogic.co.uk>,
Mike Rapoport <mike@...pulab.co.il>,
linux-kernel@...r.kernel.org
Subject: Re: Smart Battery System Design (was: Re: Question about
userspace-consumer)
On Sat, Aug 22, 2009 at 11:28:45AM +0200, Pavel Machek wrote:
> At least zaurus sl-3000c is designed like a notebook -- inactive in
> s2ram. It is quite old design.
> Charging while suspended is preffered, because it allows faster
> charge. The machine eats non-trivial power while active, charger is
> only 1A, and there's not enough current left for a charge with machine
> active.
Like you say this is a very old design but even there I'm fairly
surprised it's causing issues when charging from a wall supply. If
you're charging from USB then there is obviously a constraint on the
power draw but normally a modern system has sufficiently low power draw
when idle that it's not actually a big deal - runtime power management
facilities have improved greatly.
Some integrated PMICs will even refuse to do a fast charge when the
system is fully suspended, if only because the suspend mode of the PMIC
is intended to drive the power consumption from the PMIC itself down to
the very lowest level possible.
> > the main motiviation for going into suspend. Also bear in mind that a
> > soft SBS system requires constant activity from the CPU for basic
> > management of the charge cycle so suspend isn't going to be a real
> > option anyway, you'd be suspending for seconds at a time.
> Well, if the code is to be useful for something else than SBS... (And
> suspending for seconds at a time is okay on zaurus type machines).
It's not too bad but it's not great either - without the ability to do
things like per-device suspend during runtime (which I see is coming
along but it's not there yet) some systems end up spending a lot of the
time on bouncing the power.
There's also the fact that if you're completely reliant on the CPU to
control the charger you have to be very sure that the system will come
back from suspend reliably due to the risk of hardware damage. The
hardware should have safety features to prevent serious problems but
it's a consideration.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists