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: <20120406084140.GB3172@opensource.wolfsonmicro.com>
Date:	Fri, 6 Apr 2012 09:41:41 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	"Kim, Milo" <Milo.Kim@...com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Question about the regulator driver

On Thu, Apr 05, 2012 at 05:36:02PM -0700, Kim, Milo wrote:

> But charging termination voltage and charging current can be
> configurable in the charger operation.
> In that case, is it common to add regulator_ops for the charger ?
> Or is it better that charging parameters are set only in the power
> supply driver ?

I'd just do it as part of the power supply driver, these limits are
internal to the charger driver and so there's no real value in exporting
them.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ