linux-kernel - Re: [PATCH] regulator: adding disable options for regulator-always-on and regulator-boots-on

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: <20141103120313.GC3815@sirena.org.uk>
Date:	Mon, 3 Nov 2014 12:03:13 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Hugh Kang <hugh.kang@....com>
Cc:	Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
	jonghoon.park@....com
Subject: Re: [PATCH] regulator: adding disable options for
 regulator-always-on and regulator-boots-on

On Mon, Nov 03, 2014 at 10:26:43AM +0900, Hugh Kang wrote:
> From: "hugh.kang" <hugh.kang@....com>
> 
> If a regulator is set by always-on option, the regulator will be set forever.
> For example, suppose LDO1 is set to always-on at RevA.dts with including of a.dtsi. After that
> RevB.dts may wants to include the same a.dtsi but override the LDO1 always-on option. However,
> currently there is no way to delete the always-on option, even when we change the LDO1 option value,
> the always-on setting is still remains.

This sounds like a problem with the way the DTSs have been written - I'd
expect the thing to do here is just to move the property to the rev A
DTS when rev B is created.  Why is that not the way forward?

Otherwise this is an issue which affects any boolean property in the DT
so if it's something we need to fix we should be fixing it in a generic
fashion that will work for other properties too.

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