linux-kernel - Re: Regulator supplies when using 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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 29 Mar 2012 12:08:40 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Rajendra Nayak <rnayak@...com>
Cc:	Michael Bohan <mbohan@...eaurora.org>, lrg@...com,
	LKML <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: Regulator supplies when using Device Tree

On Thu, Mar 29, 2012 at 10:14:05AM +0530, Rajendra Nayak wrote:
> On Thursday 29 March 2012 05:36 AM, Michael Bohan wrote:
> >Put simply, whose responsibility is it to assign the
> >regulator_desc->supply_name pointer before registering a regulator
> >device added from Device Tree?

> The drivers, and its expected to know, and not lookup something from
> the DT node to figure out what regulator_desc->supply_name should
> be.

Also note that this stuff is essentially unrelated to device tree,
exactly the same mechanism should be used by all drivers it's just that
we happened to improve the framework when adding device tree support.

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