linux-kernel - Re: [PATCH 1/2] regulator: support operating mode in the device tree structure

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130507160431.GV7478@sirena.org.uk>
Date:	Tue, 7 May 2013 17:04:31 +0100
From:	Mark Brown <broonie@...nel.org>
To:	"Kim, Milo" <Milo.Kim@...com>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] regulator: support operating mode in the device tree
 structure

On Tue, May 07, 2013 at 01:09:14PM +0000, Kim, Milo wrote:
> For better power efficiency, regulator subsystem provides operating mode.
> (fast, normal, idle and standby)
> The operating mode is selective by a regulator consumer.
> 
> With this patch, regulator operating mode can be set in the DT structure.
> If any operating mode is configured, then 'valid_ops_mask' should be set with
> REGULATOR_CHANGE_MODE.

It's not clear to me that these modes are a useful thing to be exposing
in device tree - they've always been rather arbatrary and are becoming
less and less relevant as regulator hardware improves in its ability to
adapt to load.  I think for fixed modes that don't vary dynamically at
runtime the best thing is just to make the modes custom so they map onto
the device datasheets clearly.  That seems to be most of the usage
anyway.

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