linux-kernel - Re: [PATCH v3 0/4] Device tree support for regulators

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:	Thu, 27 Oct 2011 10:08:47 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Rajendra Nayak <rnayak@...com>
Cc:	grant.likely@...retlab.ca, devicetree-discuss@...ts.ozlabs.org,
	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	tony@...mide.com, lrg@...com, b-cousson@...com, patches@...aro.org,
	linux-kernel@...r.kernel.org, shawn.guo@...escale.com
Subject: Re: [PATCH v3 0/4] Device tree support for regulators

On Thu, Oct 27, 2011 at 01:26:21PM +0530, Rajendra Nayak wrote:

> v3 is based on the latest devicetree/next and is tested
> (with twl adaptaions, which will be posted seperately)
> on the OMAP4 panda and OMAP4 sdp boards.

Looking at the device bindings I notice that these bindings loose the
ability to assign a descriptive name to regulator outputs.  This is
really useful for making it easy to tie the code and the schematics
together - you can make the runing system use the same name as the
schematic.
--
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/