From: Mark Brown <broonie@kernel.org>
To: Sebastian Reichel <sre@kernel.org>
Cc: "Tim Bird" <tim.bird@sonymobile.com>,
"Rob Herring" <robh@kernel.org>,
"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>,
"dbaryshkov@gmail.com" <dbaryshkov@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"agross@codeaurora.org" <agross@codeaurora.org>,
"Andersson, Björn" <Bjorn.Andersson@sonymobile.com>,
"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 14:27:12 +0000 [thread overview]
Message-ID: <20151210142712.GM5727@sirena.org.uk> (raw)
In-Reply-To: <20151209222044.GB32712@earth>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Wed, Dec 09, 2015 at 11:20:45PM +0100, Sebastian Reichel wrote:
> On Wed, Dec 09, 2015 at 09:42:09AM -0800, Tim Bird wrote:
> > There are other switches in the charger block that are not
> > exposed yet. This one handles the the OTG (vbus) charge pathway.
> > Others handle other charge pathways (some of which are used on phones
> > and some are not - they're used, e.g., on the dragonboard). I'd
> > rather not give it a generic name, because eventually the driver
> > should expose those other switches as something as well.
> otg_regulator: regulator@0 { }
> other_regulator: regulator@1 { }
No, if this is a device with multiple regulators we have a standard way
of exposing that - have a regulators subnode with a collection of named
regulator subnodes in that. There's support for parsing this in the
framework.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-10 14:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 0:40 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 [this message]
2015-12-09 19:59 ` Bjorn Andersson
2015-12-09 21:08 ` Rob Herring
2015-12-10 15:18 ` Rob Herring
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=20151210142712.GM5727@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=Courtney.Cavin@sonymobile.com \
--cc=agross@codeaurora.org \
--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=robh@kernel.org \
--cc=sre@kernel.org \
--cc=tbird20d@gmail.com \
--cc=tim.bird@sonymobile.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
all inboxes | Powered by JetHome®