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]

Message-ID: <4F726B96.8070508@codeaurora.org>
Date:	Tue, 27 Mar 2012 18:38:30 -0700
From:	Michael Bohan <mbohan@...eaurora.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	rnayak@...com, lrg@...com, LKML <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: Regulator supplies when using Device Tree

On 3/26/2012 6:00 AM, Mark Brown wrote:
> On Thu, Mar 22, 2012 at 06:17:59PM -0700, Michael Bohan wrote:
>
>> I'm curious if there was a reason we didn't standardize on a binding
>> name for regulator supplies when using Device Tree. This appears to
>> cause duplicated code for regulator drivers that support devices
>> that may or may not have supplies specified.
>
> Supplies are *always* specified using the name from the part data sheet,
> anything to do with regulator-regulator supplies is a Linux
> implementation detail.

So before filling out the supply_name when calling regulator_register(), 
does that mean we should expect regulator drivers that optionally 
support supplies to always check with of_get_property()? And which name 
should we check? It sounds like the answer is that we should invent 
another binding to portray the name of the supply the driver should be 
checking against. But then it would seem silly to have two bindings that 
pertain to supply names.

Thanks,
Mike

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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/