From: Michael Bohan <mbohan@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: rnayak@ti.com, lrg@ti.com, LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: Regulator supplies when using Device Tree
Date: Wed, 28 Mar 2012 17:06:48 -0700 [thread overview]
Message-ID: <4F73A798.6030607@codeaurora.org> (raw)
In-Reply-To: <20120328193341.GD3232@opensource.wolfsonmicro.com>
On 3/28/2012 12:33 PM, Mark Brown wrote:
> On Wed, Mar 28, 2012 at 12:19:45PM -0700, Michael Bohan wrote:
>> Within the regulator driver, we currently have to do an
>> of_get_property(of_node, "foo-supply", NULL) to determine whether
>> the device has a supply, and thus whether we should assign
>> rdesc->supply_name to "foo" or not when calling
>
> No, this would be completely idiotic. Please think about what I'm
> saying here. To repeat, supplies of all kinds are always requested with
> the name the chip uses for the supply. This means that any machine
> binding is *totally* irrelevant to the regulator driver.
I'm not sure we're even talking about the same problem here. I agree
that the name used for the supply should correspond with the data sheet
- I just don't know how that's relevant.
Put simply, whose responsibility is it to assign the
regulator_desc->supply_name pointer before registering a regulator
device added from Device Tree? And do you agree that if you assign this
pointer to a name for which there isn't a Device Tree property specified
in that device_node, then regulator_register() will fail? This happens
because of_get_regulator() tacks on a "-supply" at the end and then
calls of_get_property() on the resulting string. That call will fail
since there is no property specified in the device_node. This is the
scenario I'm trying to avoid. Thus I add an additional check with
of_get_property() in my driver to see if the property does exist before
registering the regulator device, since both cases are reasonable. One
is a regulator device with a supply, and one is a regulator device
without a supply.
Are you aware of any other examples of submitted drivers with Device
Tree support that implement regulator devices that optionally have an
upstream supply? I looked at your tree recently and couldn't see any
such cases.
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.
next prev parent reply other threads:[~2012-03-29 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 1:17 Regulator supplies when using Device Tree Michael Bohan
2012-03-26 13:00 ` Mark Brown
2012-03-28 1:38 ` Michael Bohan
2012-03-28 10:09 ` Mark Brown
2012-03-28 19:19 ` Michael Bohan
2012-03-28 19:33 ` Mark Brown
2012-03-29 0:06 ` Michael Bohan [this message]
2012-03-29 4:44 ` Rajendra Nayak
2012-03-29 11:08 ` Mark Brown
2012-03-29 11:11 ` Mark Brown
2012-03-30 1:18 ` Michael Bohan
2012-03-30 10:36 ` Mark Brown
2012-04-02 17:35 ` Michael Bohan
2012-04-02 21:22 ` Mark Brown
2012-04-03 1:53 ` Michael Bohan
2012-04-03 12:25 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F73A798.6030607@codeaurora.org \
--to=mbohan@codeaurora.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rnayak@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).