linux-kernel - Re: [PATCH 2/3] power/ds2760_battery: make charge_now and charge_full

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]

Message-ID: <20100510132829.GM30801@buzzloop.caiaq.de>
Date:	Mon, 10 May 2010 15:28:29 +0200
From:	Daniel Mack <daniel@...aq.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org,
	Anton Vorontsov <avorontsov@...mvista.com>,
	Matt Reimer <mreimer@...p.net>,
	Evgeniy Polyakov <zbr@...emap.net>, Tejun Heo <tj@...nel.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Andres Salomon <dilinger@...labora.co.uk>,
	Alexey Starikovskiy <astarikovskiy@...e.de>,
	Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 2/3] power/ds2760_battery: make charge_now and
 charge_full_design writeable

On Mon, May 10, 2010 at 10:52:11AM +0100, Mark Brown wrote:
> On Fri, May 07, 2010 at 07:52:12PM +0200, Daniel Mack wrote:
> > For userspace tools and daemons, it might be necessary to adjust
> > the charge_now and charge_full_design properties of the ds2760 battery
> > monitor, for example for unavoidable corrections due to aging batteries.
> 
> Changing charge_full_design seems really odd - I'd really expect that to
> be something which is constant throughout the lifetime of the system.  A
> separate property showing the degraded capacity would be a bit less
> surprising.

There's 'carge_full' as well. I'll use this one instead.

Thanks,
Daniel

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