From: Ashutosh <Ashutosh.s@phytec.in>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: devicetree@vger.kernel.org, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org, s.hauer@pengutronix.de,
c.hemp@phytec.de, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, festevam@gmail.com
Subject: Re: [PATCH v3 1/4] Phytec phyFLEX-i.MX6 : Added USB_OTG Support
Date: Wed, 19 Feb 2014 12:11:41 +0530 [thread overview]
Message-ID: <53045225.50509@phytec.in> (raw)
In-Reply-To: <20140219055824.GB3010@S2101-09.ap.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
> On Wed, Feb 19, 2014 at 10:23:09AM +0800, Shawn Guo wrote:
>>> @@ -18,6 +18,14 @@
>>> memory {
>>> reg = <0x10000000 0x80000000>;
>>> };
>>> +
>>> + reg_usb_otg_vbus: regulator@0 {
>> You do not have a 'reg' property in the node, so you shouldn't have
>> '@num' in node name. You may want to name it 'regulator-0'.
> I just saw the talk between Stephen and Mark [1], and I'm with Stephen
> that neither regulator-0 nor regulator_0 is a good name. Since Mark is
> giving up the argument on the container, please follow the way we do in
> other IMX dts today.
>
> Shawn
>
> [1] http://thread.gmane.org/gmane.linux.drivers.devicetree/61894/focus=62405
>
By seeing the discussion would the below changes is appropriate
regulators {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <0>;
reg_usb_otg_vbus: regulator@0 {
compatible = "regulator-fixed";
reg = <0>;
regulator-name = "usb_otg_vbus";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
gpio = <&gpio4 15 0>;
};
But as Mark [1] suggested not to use simple bus. Which one is more
appropriate ?
[1] http://www.spinics.net/lists/linux-usb/msg101477.html
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "usb_otg_vbus";
>>> + regulator-min-microvolt = <5000000>;
>>> + regulator-max-microvolt = <5000000>;
>>> + gpio = <&gpio4 15 0>;
>>> + };
>>> };
[-- Attachment #2: Type: text/html, Size: 4112 bytes --]
next prev parent reply other threads:[~2014-02-19 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 13:46 [PATCH v3 1/4] Phytec phyFLEX-i.MX6 : Added USB_OTG Support Ashutosh singh
[not found] ` <1392731185-4885-1-git-send-email-ashutosh.s-mS2nBM426Az/PtFMR13I2A@public.gmane.org>
2014-02-18 13:46 ` [PATCH v2 2/4] Phytec phyFLEX-i.MX6 : Added USB_HOST Support Ashutosh singh
2014-02-18 13:46 ` [PATCH v2 3/4] Phytec phyFLEX-i.MX6 : Added GPMI-NAND Support Ashutosh singh
2014-02-18 13:46 ` [PATCH v2 4/4] Phytec phyFLEX-i.MX6 : Added SATA Support Ashutosh singh
2014-02-19 2:23 ` [PATCH v3 1/4] Phytec phyFLEX-i.MX6 : Added USB_OTG Support Shawn Guo
[not found] ` <20140219022307.GL15716-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2014-02-19 5:58 ` Shawn Guo
2014-02-19 6:41 ` Ashutosh [this message]
[not found] ` <53045225.50509-mS2nBM426Az/PtFMR13I2A@public.gmane.org>
2014-02-19 6:59 ` Shawn Guo
2014-02-19 6:46 ` Singh Ashutosh
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=53045225.50509@phytec.in \
--to=ashutosh.s@phytec.in \
--cc=c.hemp@phytec.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
/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).