linux-kernel - RE: Question about the regulator driver

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] [day] [month] [year] [list]

Message-ID: <B567DBAB974C0544994013492B949F8E38135B6565@EXMAIL03.scwf.nsc.com>
Date:	Fri, 6 Apr 2012 01:44:14 -0700
From:	"Kim, Milo" <Milo.Kim@...com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Question about the regulator driver

Thanks for your opinion.

Best Regards,
Milo -

> -----Original Message-----
> From: Mark Brown [mailto:broonie@...nsource.wolfsonmicro.com]
> Sent: Friday, April 06, 2012 5:42 PM
> To: Kim, Milo
> Cc: 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.
--
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/