linux-kernel - Re: [PATCH v3] Regulator: add suspend-finish API for regulator core.

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: <20110314150330.GE2626@opensource.wolfsonmicro.com>
Date:	Mon, 14 Mar 2011 15:03:30 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	MyungJoo Ham <myungjoo.ham@...sung.com>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...mlogic.co.uk>,
	kyungmin.park@...sung.com, myungjoo.ham@...il.com,
	Igor Grinberg <grinberg@...pulab.co.il>
Subject: Re: [PATCH v3] Regulator: add suspend-finish API for regulator
 core.

On Fri, Mar 11, 2011 at 10:13:59AM +0900, MyungJoo Ham wrote:
> The regulator core had suspend-prepare that turns off the regulators
> when entering a system-wide suspend. However, it did not have
> suspend-finish that pairs with suspend-prepare and the regulator core
> has assumed that the regulator devices and their drivers support
> autonomous recover at resume.

Acked-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>

We should be doing this automatically as part of the core but since
we've not done that for suspend yet it seems reasonable to apply as-is
then fix both the teardown and powerup paths together.  Since the code
won't be called unless someone explicitly does so there's very little
risk here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/