From: Benoit Cousson <b-cousson@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: <balbi@ti.com>, <linux@arm.linux.org.uk>,
<rob.herring@calxeda.com>, <grant.likely@secretlab.ca>,
<tony@atomide.com>, <rnayak@ti.com>, <hvaibhav@ti.com>,
<peter.ujfalusi@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] arm/dts: Add twl4030-usb data
Date: Tue, 11 Sep 2012 12:09:34 +0200 [thread overview]
Message-ID: <504F0DDE.308@ti.com> (raw)
In-Reply-To: <1347345381-4390-3-git-send-email-kishon@ti.com>
On 09/11/2012 08:36 AM, Kishon Vijay Abraham I wrote:
> Add twl4030-usb data node in twl4030 device tree file.
IIRC, the usb part on twl4030 was doing more than it does on twl6030.
Could you describe what part of the USB is really done by the TWL in
that case?
> Acked-by: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> ---
> arch/arm/boot/dts/twl4030.dtsi | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
> index 22f4d13..761a5a5 100644
> --- a/arch/arm/boot/dts/twl4030.dtsi
> +++ b/arch/arm/boot/dts/twl4030.dtsi
> @@ -37,6 +37,18 @@
> regulator-max-microvolt = <3150000>;
> };
>
> + vusb1v5: regulator-vusb1v5 {
> + compatible = "ti,twl4030-vusb1v5";
> + };
> +
> + vusb1v8: regulator-vusb1v8 {
> + compatible = "ti,twl4030-vusb1v8";
> + };
> +
> + vusb3v1: regulator-vusb3v1 {
> + compatible = "ti,twl4030-vusb3v1";
> + };
> +
> twl_gpio: gpio {
> compatible = "ti,twl4030-gpio";
> gpio-controller;
> @@ -44,4 +56,13 @@
> interrupt-controller;
> #interrupt-cells = <1>;
> };
> +
> + twl4030-usb {
Same comment than before about the name. Is it the usb-comparator as well?
> + compatible = "ti,twl4030-usb";
> + interrupts = < 10 4 >;
> + usb1v5-supply = <&vusb1v5>;
> + usb1v8-supply = <&vusb1v8>;
> + usb3v1-supply = <&vusb3v1>;
> + usb_mode = <1>;
Is this a TI only attribute or something generic?
If this is TI only, it should be prefix with "ti," otherwise, it is fine.
Regards,
Benoit
next prev parent reply other threads:[~2012-09-11 10:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 6:36 [PATCH v2 0/3] arm/dts: omap: add dt data for MUSB Kishon Vijay Abraham I
2012-09-11 6:36 ` [PATCH v2 1/3] arm/dts: Add twl6030-usb data Kishon Vijay Abraham I
2012-09-11 9:26 ` Benoit Cousson
2012-09-11 9:39 ` ABRAHAM, KISHON VIJAY
2012-09-11 10:05 ` Benoit Cousson
2012-09-11 6:36 ` [PATCH v2 2/3] arm/dts: Add twl4030-usb data Kishon Vijay Abraham I
2012-09-11 10:09 ` Benoit Cousson [this message]
2012-09-11 11:07 ` ABRAHAM, KISHON VIJAY
2012-09-11 6:36 ` [PATCH v2 3/3] arm/dts: omap: Add usb_otg and glue data Kishon Vijay Abraham I
2012-09-11 10:18 ` Benoit Cousson
2012-09-11 8:25 ` [PATCH v2 0/3] arm/dts: omap: add dt data for MUSB Benoit Cousson
2012-09-11 8:44 ` ABRAHAM, KISHON VIJAY
2012-09-11 9:11 ` Benoit Cousson
2012-09-11 9:16 ` ABRAHAM, KISHON VIJAY
2012-09-11 10:01 ` Benoit Cousson
2012-09-11 10:19 ` Benoit Cousson
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=504F0DDE.308@ti.com \
--to=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=hvaibhav@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peter.ujfalusi@ti.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=tony@atomide.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