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-next>] [day] [month] [year] [list]
Message-ID: <B567DBAB974C0544994013492B949F8E38135B639C@EXMAIL03.scwf.nsc.com>
Date:	Thu, 5 Apr 2012 17:36:02 -0700
From:	"Kim, Milo" <Milo.Kim@...com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Question about the regulator driver

Hello,

I have a question about the regulator driver design.

There is a mfd device including charger and regulator functions.

For supporting DCDC(or BUCK) and LDO functions, the regulator driver is used.
(like setting voltage, current limit and so on)
On the other hand, the charger module is registered as the power supply class driver.

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 like to have your opinion.

Thanks & BR
Milo -

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