From: Rob Herring <robh@kernel.org>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: "Bird, Tim" <Tim.Bird@sonymobile.com>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"sre@kernel.org" <sre@kernel.org>,
"dbaryshkov@gmail.com" <dbaryshkov@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"agross@codeaurora.org" <agross@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tbird20d@gmail.com" <tbird20d@gmail.com>,
"Cavin, Courtney" <Courtney.Cavin@sonymobile.com>
Subject: Re: [PATCH v2 1/3] dt-binding: power: Add otg regulator binding
Date: Thu, 10 Dec 2015 09:18:23 -0600 [thread overview]
Message-ID: <CAL_Jsq+w0ide6kkwCgQPxZ6dbL0MrSEBxe6XnjcsECP9_zRV7g@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKV=AucyZvFaxsSrZ5Hn718ZMKDfd8pqLHFT27RbE7VMA@mail.gmail.com>
On Wed, Dec 9, 2015 at 3:08 PM, Rob Herring <robh@kernel.org> wrote:
> On Wed, Dec 9, 2015 at 1:59 PM, Bjorn Andersson
> <bjorn.andersson@sonymobile.com> wrote:
>> On Wed 09 Dec 06:36 PST 2015, Rob Herring wrote:
>>
>>> On Wed, Dec 9, 2015 at 6:55 AM, Tim Bird <tim.bird@sonymobile.com> wrote:
>>> > On 12/08/2015 08:11 PM, Rob Herring wrote:
>>> >> On Tue, Dec 08, 2015 at 04:40:16PM -0800, Tim Bird wrote:
>>> >>> Add a binding for the regulator which controls the OTG chargepath switch.
>>> >>> The OTG switch gets its power from pm8941_5vs1, and that should be
>>> >>> expressed as a usb-otg-in-supply property in the DT node for the
>>> >>> charger driver. The regulator name is "otg".
>>>
>>> [...]
>>>
>>> >>> +child nodes:
>>> >>> +- otg:
>>> >>> + Usage: optional
>>> >>> + Description: This node defines a regulator used to control the direction
>>> >>> + of VBUS voltage - specifically: whether to supply voltage
>>> >>> + to VBUS for host mode operation of the OTG port, or allow
>>> >>> + input voltage from external VBUS for charging. In the
>>> >>> + hardware, the supply for this regulator comes from
>>> >>> + usb-otg-in-supply.
>>> >>
>>> >> Doesn't this regulator need to have a name defined?
>>> >
>>> > I'm not sure what you mean. The regulator name is "otg", defined by the DT node
>>> > name. The code requires that the DT node name be "otg", and defines a regulator
>>> > with the same name.
>>> >
>>> > As far as I know, you have to define a DT label for the node, in order
>>> > to reference this regulator with a phandle. Is that what you are referring to?
>>> > I usually use "chg_otg" as the label. Are you asking that this be reflected
>>> > in the example?
>>>
>>> You need a regulator-name property. Also, should should define valid
>>> values for regulator-min-microvolt and regulator-max-microvolt.
>>>
>>
>> The regulator has a name, derived from the node name, and this is
>> significant. If the developer wants an additional human readable name
>> for some reason they can use the optional regulator-name property.
>>
>> The regulator is a simple switch and as such inherits voltage properties
>> from its supply. It should therefor not have any specified voltage
>> range.
>>
>>> Thinking about this some more, the node name should be generic, so
>>> just "regulator". The label does not need to be generic.
>>>
>>
>> The name of the node is significant, as it's used for matching the
>> regulator to an implementation.
>
> Ah yes, you are right. I forget what an oddball the regulator binding is.
>
> And if voltage switches don't need min and max properties, then it is
> fine as is. Still, the empty node with no properties seems odd to me.
Thinking some more about this, what bothers me is just having "otg
{};" gives no clue as to what the node is for w/o the documentation.
"otg" alone could mean several things. I think minimally, it needs
either a node name that gives some indication it is a regulator or
Vbus supply, a required regulator-name or even a comment.
Rob
prev parent reply other threads:[~2015-12-10 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 0:40 [PATCH v2 1/3] dt-binding: power: Add otg regulator binding Tim Bird
2015-12-09 0:40 ` [PATCH v2 2/3] power: qcom_smbb: Add otg regulator for control of vbus Tim Bird
2015-12-09 0:40 ` [PATCH v2 3/3] ARM: dts: qcom: add charger otg regulator Tim Bird
2015-12-09 4:11 ` [PATCH v2 1/3] dt-binding: power: Add otg regulator binding Rob Herring
2015-12-09 12:55 ` Tim Bird
2015-12-09 14:36 ` Rob Herring
2015-12-09 17:42 ` Tim Bird
2015-12-09 18:56 ` Mark Brown
2015-12-09 22:20 ` Sebastian Reichel
2015-12-10 14:27 ` Mark Brown
2015-12-09 19:59 ` Bjorn Andersson
2015-12-09 21:08 ` Rob Herring
2015-12-10 15:18 ` Rob Herring [this message]
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=CAL_Jsq+w0ide6kkwCgQPxZ6dbL0MrSEBxe6XnjcsECP9_zRV7g@mail.gmail.com \
--to=robh@kernel.org \
--cc=Courtney.Cavin@sonymobile.com \
--cc=Tim.Bird@sonymobile.com \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=sre@kernel.org \
--cc=tbird20d@gmail.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).