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] [day] [month] [year] [list]

Date:	Fri, 26 Jul 2013 23:42:44 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Tomasz Figa <tomasz.figa@...il.com>
Cc:	Vincent Palatin <vpalatin@...omium.org>,
	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 Fri, Jul 26, 2013 at 10:54:10PM +0200, Tomasz Figa wrote:

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

> We do have such boards at Samsung. Actually I made a similar patch for our 
> internal tree.

Do you have more details on what exactly is happening with this stuff
and why it isn't dynamic.  Like I say suspend to disk seems relatively
easy but suspend to RAM gets a bit tricky these days.

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