lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 21 Aug 2009 16:01:26 +0200
From:	Pavel Machek <pavel@....cz>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
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 2009-08-22 11:16:42, Mark Brown wrote:
> 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.

Well... all the hardware I have here (zaurus, openmoko, htc dream) has
issues with power consumption while charging... so I do not think
runtime pm is solved problem.

> 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.

While crashes during suspend/resume are common on pcs, embedded
systens do better. And crashes during runtime happen, too.

First, I can't imagine system where you can damage the battery by just
crashing sw. 4.2 per cell voltage limit is just too easy to do in
hw. Maybe if you crash the sw then bring the machine outside while its
stil on charger and theres 110F outside...

And yes it should have safety features, and if they are not there its
broken hw.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ