linux-kernel - Re: [PATCH] regulator: read low power states configuration from device tree

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: <20130725200343.GV9858@sirena.org.uk>
Date:	Thu, 25 Jul 2013 21:03:43 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Vincent Palatin <vpalatin@...omium.org>
Cc:	Grant Likely <grant.likely@...aro.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	linux-kernel@...r.kernel.org, Olof Johansson <olofj@...omium.org>,
	devicetree@...r.kernel.org
Subject: Re: [PATCH] regulator: read low power states configuration from
 device tree

On Thu, Jul 25, 2013 at 12:42:00PM -0700, Vincent Palatin wrote:

> +- regulator-suspend-disk-microvolt: voltage applied when entering S2D
> +- regulator-suspend-disk-disabled: turn off when entering S2D
> +- regulator-suspend-mem-microvolt: voltage applied when entering S2M
> +- regulator-suspend-mem-disabled: turn off when entering S2M
> +- regulator-suspend-standby-microvolt: voltage applied when entering standby
> +- regulator-suspend-standby-disabled: turn off when entering standby

The reason this isn't in device tree at the minute is that suspend to
disk and suspend to RAM are somewhat Linux specific concepts and the
whole thing gets more and more dynamic as time moves forwards with the
suspend state for practical systems depending on the instantaneous
device state prior to entering suspend and the bits that are fixed often
involving sequencing elements and so on which get fixed in hardware
and/or bootloader.  Do you have practical systems where this is needed?

It's also not clear to me hat the -disabled properties make sense; if we
have properties for the state when enabled I'd expect them to allow
things to be marked as enabled or disabled (with don't touch as the
default).

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