linux-kernel - Re: [PATCH 1/2] AB3100 regulator support v3

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]

Message-ID: <20090902215533.GA18527@opensource.wolfsonmicro.com>
Date:	Wed, 2 Sep 2009 22:55:33 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Linus Walleij <linus.ml.walleij@...il.com>
Cc:	Linus Walleij <linus.walleij@...ricsson.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH 1/2] AB3100 regulator support v3

On Wed, Sep 02, 2009 at 11:37:00PM +0200, Linus Walleij wrote:

> The sleep settings are driven by two HW lines, so a regulator
> can react by suspending the regulator on line A or B disjunct
> either (logical ||) or both (logical &&). (You don't alter that in
> runtime so no API has been developed here.)

OK, that's fine - it's setting things outside the normal API flow which
is all that I was asking.

> And I don't see any way for the core (set_machine_constraints)
> to set regulators to *off* by default if they happen to be on at
> boot.

That'd be a boot_off constraint if someone requires it.  So far nobody
has - there's not going to be many cases where it's appropriate to do
so, normally either you want to leave the supplies on for the device
driver that's taking control of the device or it does no harm to wait
till the end of init.
--
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/