linux-kernel - Re: parent/child hierarchy for regulator

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: <20150305122234.GL21293@sirena.org.uk>
Date:	Thu, 5 Mar 2015 12:22:34 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Peter Chen <peter.chen@...escale.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	lgirdwood@...il.com
Subject: Re: parent/child hierarchy for regulator

On Thu, Mar 05, 2015 at 06:35:36PM +0800, Peter Chen wrote:

> Any good ways at code/dts to show parent/child hierarchy for regulator?

There's plenty of examples in mainline...

> The related regulators at my platforms like below:
> PMIC (SWB 5v) --> Switch Chip (GPIO Regulator) --> USB VBUS

> PMIC has one 5V regulator (eg, swbst at pfuse), and it is the input
> for USB power switch chip, and there are two gpios at this switch
> chip to control if 5V is output or not, we register these two gpios as 
> fixed regulators, currently, if regulator swbst is disabled, the
> gpio regulator has no way to know, and cause the vbus voltage is wrong.

Can you please clarify why you're registering two fixed voltage
regulators for the switch chip and how you're doing that?  The picture
above looks like you should just have a single regulator there and
nothing should care if the either regulator is enabled when querying the
parent for its voltage.

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