linux-kernel - Re: [PATCH v2] regulator: gpio-regulator: add DT bindings

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]

Date:	Tue, 11 Sep 2012 07:41:46 +0800
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Daniel Mack <zonque@...il.com>,
	devicetree-discuss@...ts.ozlabs.org, lrg@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] regulator: gpio-regulator: add DT bindings

On Mon, Sep 10, 2012 at 01:40:36PM -0600, Stephen Warren wrote:
> On 09/10/2012 09:03 AM, Daniel Mack wrote:

> > + - "enabled-at-boot":		If set, the regulator has been enabled at boot
> > +				time

> Isn't that regulator-boot-on, as defined in regulator.txt that you
> mentioned?

It's slightly different due to our unfortunate inability to support
GPIO readback for output GPIOs - this means the regualtor is enabled at
boot and the driver should use that to bootstrap state, the core one
means the regulator should be turned on at boot.  The latter would force
the regulator to be be enabled during boot.
--
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/