From: kishon@ti•com (kishon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
Date: Thu, 7 Feb 2013 12:01:59 +0530 [thread overview]
Message-ID: <51134A5F.1090707@ti.com> (raw)
In-Reply-To: <511347E8.2030604@ti.com>
Hi,
On Thursday 07 February 2013 11:51 AM, Rajendra Nayak wrote:
> []...
>
>>
>> diff --git a/Documentation/devicetree/bindings/usb/omap-usb.txt
>> b/Documentation/devicetree/bindings/usb/omap-usb.txt
>> index 29a043e..4688265 100644
>> --- a/Documentation/devicetree/bindings/usb/omap-usb.txt
>> +++ b/Documentation/devicetree/bindings/usb/omap-usb.txt
>> @@ -15,6 +15,7 @@ OMAP MUSB GLUE
>> represents PERIPHERAL.
>> - power : Should be "50". This signifies the controller can supply
>> upto
>> 100mA when operating in host mode.
>> + - usb-phy : the phandle for the PHY device
>>
>> SOC specific device node entry
>> usb_otg_hs: usb_otg_hs at 4a0ab000 {
>> diff --git a/arch/arm/boot/dts/omap3-beagle-xm.dts
>> b/arch/arm/boot/dts/omap3-beagle-xm.dts
>> index 3705a81..cb07583 100644
>> --- a/arch/arm/boot/dts/omap3-beagle-xm.dts
>> +++ b/arch/arm/boot/dts/omap3-beagle-xm.dts
>> @@ -107,3 +107,9 @@
>> */
>> ti,pulldowns = <0x03a1c4>;
>> };
>> +
>> +&usb_otg_hs {
>> + interface_type = <0>;
>> + mode = <3>;
>> + power = <50>;
>> +};
>> diff --git a/arch/arm/boot/dts/omap3-evm.dts
>> b/arch/arm/boot/dts/omap3-evm.dts
>> index e8ba1c2..afb9ba9 100644
>> --- a/arch/arm/boot/dts/omap3-evm.dts
>> +++ b/arch/arm/boot/dts/omap3-evm.dts
>> @@ -59,3 +59,9 @@
>> &twl_gpio {
>> ti,use-leds;
>> };
>> +
>> +&usb_otg_hs {
>> + interface_type = <0>;
>> + mode = <3>;
>> + power = <50>;
>> +};
>> diff --git a/arch/arm/boot/dts/omap3-overo.dtsi
>> b/arch/arm/boot/dts/omap3-overo.dtsi
>> index 89808ce..4b3d157 100644
>> --- a/arch/arm/boot/dts/omap3-overo.dtsi
>> +++ b/arch/arm/boot/dts/omap3-overo.dtsi
>> @@ -55,3 +55,9 @@
>> &twl_gpio {
>> ti,use-leds;
>> };
>> +
>> +&usb_otg_hs {
>> + interface_type = <0>;
>> + mode = <3>;
>> + power = <50>;
>> +};
>> diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
>> index 1acc261..b6472f7 100644
>> --- a/arch/arm/boot/dts/omap3.dtsi
>> +++ b/arch/arm/boot/dts/omap3.dtsi
>> @@ -397,5 +397,17 @@
>> ti,timer-alwon;
>> ti,timer-secure;
>> };
>> +
>> + usb_otg_hs: usb_otg_hs at 480ab000 {
>> + compatible = "ti,omap3-musb";
>> + reg = <0x480ab000 0x1000>;
>> + interrupts = <0 92 0x4>, <0 93 0x4>;
>> + interrupt-names = "mc", "dma";
>> + ti,hwmods = "usb_otg_hs";
>> + usb-phy = <&usb2_phy>;
>> + multipoint = <1>;
>> + num_eps = <16>;
>> + ram_bits = <12>;
>
> Where are these bindings documented? The general convention is to use
> a '-' for property names and not '_'
It's documented in Documentation/devicetree/bindings/usb/omap-usb.txt
Actually the documentation and the drivers got merged with this binding
long back.
Thanks
Kishon
next prev parent reply other threads:[~2013-02-07 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 14:56 [PATCH 0/8] ARM: dts: omap: Add dts data for USB Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 1/8] ARM: dts: omap: Add omap control usb data Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 2/8] ARM: dts: omap: Add omap-usb2 dt data Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data Kishon Vijay Abraham I
2013-02-07 6:21 ` Rajendra Nayak
2013-02-07 6:31 ` kishon [this message]
2013-02-06 14:56 ` [PATCH 4/8] ARM: dts: omap5: Add omap control usb data Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 5/8] ARM: dts: omap5: Add ocp2scp data Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 6/8] ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 7/8] ARM: dts: omap5: add dwc3 omap " Kishon Vijay Abraham I
2013-02-06 14:56 ` [PATCH 8/8] ARM: dts: omap5: add dwc3 core " Kishon Vijay Abraham I
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=51134A5F.1090707@ti.com \
--to=kishon@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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