* [PATCH 0/8] ARM: dts: omap: Add dts data for USB
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
This series applies cleanly in both for_3.9/dts and 3.8-rc6.
All the patches deal with modifying arch/arm/boot except one which modifies
Documentation/../usb/omap-usb.txt
Kishon Vijay Abraham I (8):
ARM: dts: omap: Add omap control usb data
ARM: dts: omap: Add omap-usb2 dt data
ARM: dts: omap: Add usb_otg and glue data
ARM: dts: omap5: Add omap control usb data
ARM: dts: omap5: Add ocp2scp data
ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data
ARM: dts: omap5: add dwc3 omap dt data
ARM: dts: omap5: add dwc3 core dt data
Documentation/devicetree/bindings/usb/omap-usb.txt | 1 +
arch/arm/boot/dts/omap3-beagle-xm.dts | 6 +++
arch/arm/boot/dts/omap3-evm.dts | 6 +++
arch/arm/boot/dts/omap3-overo.dtsi | 6 +++
arch/arm/boot/dts/omap3.dtsi | 12 +++++
arch/arm/boot/dts/omap4-panda.dts | 6 +++
arch/arm/boot/dts/omap4-sdp.dts | 6 +++
arch/arm/boot/dts/omap4.dtsi | 26 +++++++++++
arch/arm/boot/dts/omap5.dtsi | 48 ++++++++++++++++++++
arch/arm/boot/dts/twl4030.dtsi | 2 +-
10 files changed, 118 insertions(+), 1 deletion(-)
--
1.7.10.4
^ permalink raw reply [flat|nested] 33+ messages in thread
* [PATCH 0/8] ARM: dts: omap: Add dts data for USB
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson-l0cyMroinI0, tony-4v6yS6AI5VpBDgjK7y7TUQ,
linux-lFZ/pmaqli7XmaaqVzeoHQ, rob.herring-bsGFqQB8/DxBDgjK7y7TUQ,
rob-VoJi6FS/r0vR7s880joybQ, balbi-l0cyMroinI0,
linux-usb-u79uwXL29TY76Z2rM5mHXA,
linux-omap-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r, kishon-l0cyMroinI0
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
This series applies cleanly in both for_3.9/dts and 3.8-rc6.
All the patches deal with modifying arch/arm/boot except one which modifies
Documentation/../usb/omap-usb.txt
Kishon Vijay Abraham I (8):
ARM: dts: omap: Add omap control usb data
ARM: dts: omap: Add omap-usb2 dt data
ARM: dts: omap: Add usb_otg and glue data
ARM: dts: omap5: Add omap control usb data
ARM: dts: omap5: Add ocp2scp data
ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data
ARM: dts: omap5: add dwc3 omap dt data
ARM: dts: omap5: add dwc3 core dt data
Documentation/devicetree/bindings/usb/omap-usb.txt | 1 +
arch/arm/boot/dts/omap3-beagle-xm.dts | 6 +++
arch/arm/boot/dts/omap3-evm.dts | 6 +++
arch/arm/boot/dts/omap3-overo.dtsi | 6 +++
arch/arm/boot/dts/omap3.dtsi | 12 +++++
arch/arm/boot/dts/omap4-panda.dts | 6 +++
arch/arm/boot/dts/omap4-sdp.dts | 6 +++
arch/arm/boot/dts/omap4.dtsi | 26 +++++++++++
arch/arm/boot/dts/omap5.dtsi | 48 ++++++++++++++++++++
arch/arm/boot/dts/twl4030.dtsi | 2 +-
10 files changed, 118 insertions(+), 1 deletion(-)
--
1.7.10.4
^ permalink raw reply [flat|nested] 33+ messages in thread
* [PATCH 1/8] ARM: dts: omap: Add omap control usb data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap4.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 739bb79..ffc7352 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -529,5 +529,13 @@
ti,hwmods = "timer11";
ti,timer-pwm;
};
+
+ omap_control_usb: omap-control-usb@4a002300 {
+ compatible = "ti,omap-control-usb";
+ reg = <0x4a002300 0x4>,
+ <0x4a00233c 0x4>;
+ reg-names = "control_dev_conf", "otghs_control";
+ ti,type = <1>;
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 1/8] ARM: dts: omap: Add omap control usb data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap4.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 739bb79..ffc7352 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -529,5 +529,13 @@
ti,hwmods = "timer11";
ti,timer-pwm;
};
+
+ omap_control_usb: omap-control-usb at 4a002300 {
+ compatible = "ti,omap-control-usb";
+ reg = <0x4a002300 0x4>,
+ <0x4a00233c 0x4>;
+ reg-names = "control_dev_conf", "otghs_control";
+ ti,type = <1>;
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 1/8] ARM: dts: omap: Add omap control usb data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson-l0cyMroinI0, tony-4v6yS6AI5VpBDgjK7y7TUQ,
linux-lFZ/pmaqli7XmaaqVzeoHQ, rob.herring-bsGFqQB8/DxBDgjK7y7TUQ,
rob-VoJi6FS/r0vR7s880joybQ, balbi-l0cyMroinI0,
linux-usb-u79uwXL29TY76Z2rM5mHXA,
linux-omap-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r, kishon-l0cyMroinI0
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>
---
arch/arm/boot/dts/omap4.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 739bb79..ffc7352 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -529,5 +529,13 @@
ti,hwmods = "timer11";
ti,timer-pwm;
};
+
+ omap_control_usb: omap-control-usb@4a002300 {
+ compatible = "ti,omap-control-usb";
+ reg = <0x4a002300 0x4>,
+ <0x4a00233c 0x4>;
+ reg-names = "control_dev_conf", "otghs_control";
+ ti,type = <1>;
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread
* [PATCH 2/8] ARM: dts: omap: Add omap-usb2 dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap4.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index ffc7352..c829d7e 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -438,6 +438,11 @@
#size-cells = <1>;
ranges;
ti,hwmods = "ocp2scp_usb_phy";
+ usb2_phy: usb2phy@4a0ad080 {
+ compatible = "ti,omap-usb2";
+ reg = <0x4a0ad080 0x58>;
+ ctrl-module = <&omap_control_usb>;
+ };
};
timer1: timer@4a318000 {
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 2/8] ARM: dts: omap: Add omap-usb2 dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap4.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index ffc7352..c829d7e 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -438,6 +438,11 @@
#size-cells = <1>;
ranges;
ti,hwmods = "ocp2scp_usb_phy";
+ usb2_phy: usb2phy at 4a0ad080 {
+ compatible = "ti,omap-usb2";
+ reg = <0x4a0ad080 0x58>;
+ ctrl-module = <&omap_control_usb>;
+ };
};
timer1: timer at 4a318000 {
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 2/8] ARM: dts: omap: Add omap-usb2 dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson-l0cyMroinI0, tony-4v6yS6AI5VpBDgjK7y7TUQ,
linux-lFZ/pmaqli7XmaaqVzeoHQ, rob.herring-bsGFqQB8/DxBDgjK7y7TUQ,
rob-VoJi6FS/r0vR7s880joybQ, balbi-l0cyMroinI0,
linux-usb-u79uwXL29TY76Z2rM5mHXA,
linux-omap-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ
Cc: grant.likely-s3s/WqlpOiPyB63q8FvJNQ,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r, kishon-l0cyMroinI0
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
Signed-off-by: Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>
---
arch/arm/boot/dts/omap4.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index ffc7352..c829d7e 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -438,6 +438,11 @@
#size-cells = <1>;
ranges;
ti,hwmods = "ocp2scp_usb_phy";
+ usb2_phy: usb2phy@4a0ad080 {
+ compatible = "ti,omap-usb2";
+ reg = <0x4a0ad080 0x58>;
+ ctrl-module = <&omap_control_usb>;
+ };
};
timer1: timer@4a318000 {
--
1.7.10.4
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply related [flat|nested] 33+ messages in thread
* [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-<board>.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host mode.
The information about usb otg node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Acked-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 1 +
arch/arm/boot/dts/omap3-beagle-xm.dts | 6 ++++++
arch/arm/boot/dts/omap3-evm.dts | 6 ++++++
arch/arm/boot/dts/omap3-overo.dtsi | 6 ++++++
arch/arm/boot/dts/omap3.dtsi | 12 ++++++++++++
arch/arm/boot/dts/omap4-panda.dts | 6 ++++++
arch/arm/boot/dts/omap4-sdp.dts | 6 ++++++
arch/arm/boot/dts/omap4.dtsi | 13 +++++++++++++
arch/arm/boot/dts/twl4030.dtsi | 2 +-
9 files changed, 57 insertions(+), 1 deletion(-)
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@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@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>;
+ };
};
};
diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
index 4122efe..612c9bb 100644
--- a/arch/arm/boot/dts/omap4-panda.dts
+++ b/arch/arm/boot/dts/omap4-panda.dts
@@ -206,3 +206,9 @@
&twl_usb_comparator {
usb-supply = <&vusb>;
};
+
+&usb_otg_hs {
+ interface_type = <1>;
+ mode = <3>;
+ power = <50>;
+};
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 43e5258..582d7ee 100644
--- a/arch/arm/boot/dts/omap4-sdp.dts
+++ b/arch/arm/boot/dts/omap4-sdp.dts
@@ -428,3 +428,9 @@
&twl_usb_comparator {
usb-supply = <&vusb>;
};
+
+&usb_otg_hs {
+ interface_type = <1>;
+ mode = <3>;
+ power = <50>;
+};
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index c829d7e..5171739 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -542,5 +542,18 @@
reg-names = "control_dev_conf", "otghs_control";
ti,type = <1>;
};
+
+ usb_otg_hs: usb_otg_hs@4a0ab000 {
+ compatible = "ti,omap4-musb";
+ reg = <0x4a0ab000 0x7ff>;
+ 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>;
+ ti,has-mailbox;
+ };
};
};
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index ed0bc95..398d2c3 100644
--- a/arch/arm/boot/dts/twl4030.dtsi
+++ b/arch/arm/boot/dts/twl4030.dtsi
@@ -67,7 +67,7 @@
#interrupt-cells = <1>;
};
- twl4030-usb {
+ usb2_phy: twl4030-usb {
compatible = "ti,twl4030-usb";
interrupts = <10>, <4>;
usb1v5-supply = <&vusb1v5>;
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-<board>.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host mode.
The information about usb otg node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Acked-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 1 +
arch/arm/boot/dts/omap3-beagle-xm.dts | 6 ++++++
arch/arm/boot/dts/omap3-evm.dts | 6 ++++++
arch/arm/boot/dts/omap3-overo.dtsi | 6 ++++++
arch/arm/boot/dts/omap3.dtsi | 12 ++++++++++++
arch/arm/boot/dts/omap4-panda.dts | 6 ++++++
arch/arm/boot/dts/omap4-sdp.dts | 6 ++++++
arch/arm/boot/dts/omap4.dtsi | 13 +++++++++++++
arch/arm/boot/dts/twl4030.dtsi | 2 +-
9 files changed, 57 insertions(+), 1 deletion(-)
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>;
+ };
};
};
diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
index 4122efe..612c9bb 100644
--- a/arch/arm/boot/dts/omap4-panda.dts
+++ b/arch/arm/boot/dts/omap4-panda.dts
@@ -206,3 +206,9 @@
&twl_usb_comparator {
usb-supply = <&vusb>;
};
+
+&usb_otg_hs {
+ interface_type = <1>;
+ mode = <3>;
+ power = <50>;
+};
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 43e5258..582d7ee 100644
--- a/arch/arm/boot/dts/omap4-sdp.dts
+++ b/arch/arm/boot/dts/omap4-sdp.dts
@@ -428,3 +428,9 @@
&twl_usb_comparator {
usb-supply = <&vusb>;
};
+
+&usb_otg_hs {
+ interface_type = <1>;
+ mode = <3>;
+ power = <50>;
+};
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index c829d7e..5171739 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -542,5 +542,18 @@
reg-names = "control_dev_conf", "otghs_control";
ti,type = <1>;
};
+
+ usb_otg_hs: usb_otg_hs at 4a0ab000 {
+ compatible = "ti,omap4-musb";
+ reg = <0x4a0ab000 0x7ff>;
+ 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>;
+ ti,has-mailbox;
+ };
};
};
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index ed0bc95..398d2c3 100644
--- a/arch/arm/boot/dts/twl4030.dtsi
+++ b/arch/arm/boot/dts/twl4030.dtsi
@@ -67,7 +67,7 @@
#interrupt-cells = <1>;
};
- twl4030-usb {
+ usb2_phy: twl4030-usb {
compatible = "ti,twl4030-usb";
interrupts = <10>, <4>;
usb1v5-supply = <&vusb1v5>;
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson-l0cyMroinI0, tony-4v6yS6AI5VpBDgjK7y7TUQ,
linux-lFZ/pmaqli7XmaaqVzeoHQ, rob.herring-bsGFqQB8/DxBDgjK7y7TUQ,
rob-VoJi6FS/r0vR7s880joybQ, balbi-l0cyMroinI0,
linux-usb-u79uwXL29TY76Z2rM5mHXA,
linux-omap-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r, kishon-l0cyMroinI0
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-<board>.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host mode.
The information about usb otg node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Acked-by: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
Signed-off-by: Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 1 +
arch/arm/boot/dts/omap3-beagle-xm.dts | 6 ++++++
arch/arm/boot/dts/omap3-evm.dts | 6 ++++++
arch/arm/boot/dts/omap3-overo.dtsi | 6 ++++++
arch/arm/boot/dts/omap3.dtsi | 12 ++++++++++++
arch/arm/boot/dts/omap4-panda.dts | 6 ++++++
arch/arm/boot/dts/omap4-sdp.dts | 6 ++++++
arch/arm/boot/dts/omap4.dtsi | 13 +++++++++++++
arch/arm/boot/dts/twl4030.dtsi | 2 +-
9 files changed, 57 insertions(+), 1 deletion(-)
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@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@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>;
+ };
};
};
diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
index 4122efe..612c9bb 100644
--- a/arch/arm/boot/dts/omap4-panda.dts
+++ b/arch/arm/boot/dts/omap4-panda.dts
@@ -206,3 +206,9 @@
&twl_usb_comparator {
usb-supply = <&vusb>;
};
+
+&usb_otg_hs {
+ interface_type = <1>;
+ mode = <3>;
+ power = <50>;
+};
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
index 43e5258..582d7ee 100644
--- a/arch/arm/boot/dts/omap4-sdp.dts
+++ b/arch/arm/boot/dts/omap4-sdp.dts
@@ -428,3 +428,9 @@
&twl_usb_comparator {
usb-supply = <&vusb>;
};
+
+&usb_otg_hs {
+ interface_type = <1>;
+ mode = <3>;
+ power = <50>;
+};
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index c829d7e..5171739 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -542,5 +542,18 @@
reg-names = "control_dev_conf", "otghs_control";
ti,type = <1>;
};
+
+ usb_otg_hs: usb_otg_hs@4a0ab000 {
+ compatible = "ti,omap4-musb";
+ reg = <0x4a0ab000 0x7ff>;
+ 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>;
+ ti,has-mailbox;
+ };
};
};
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
index ed0bc95..398d2c3 100644
--- a/arch/arm/boot/dts/twl4030.dtsi
+++ b/arch/arm/boot/dts/twl4030.dtsi
@@ -67,7 +67,7 @@
#interrupt-cells = <1>;
};
- twl4030-usb {
+ usb2_phy: twl4030-usb {
compatible = "ti,twl4030-usb";
interrupts = <10>, <4>;
usb1v5-supply = <&vusb1v5>;
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* Re: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
2013-02-06 14:56 ` Kishon Vijay Abraham I
(?)
@ 2013-02-07 6:21 ` Rajendra Nayak
-1 siblings, 0 replies; 33+ messages in thread
From: Rajendra Nayak @ 2013-02-07 6:21 UTC (permalink / raw)
To: Kishon Vijay Abraham I
Cc: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss, gregkh
[]...
>
> 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@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@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 '_'
> + };
> };
> };
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index 4122efe..612c9bb 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -206,3 +206,9 @@
> &twl_usb_comparator {
> usb-supply = <&vusb>;
> };
> +
> +&usb_otg_hs {
> + interface_type = <1>;
> + mode = <3>;
> + power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 43e5258..582d7ee 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -428,3 +428,9 @@
> &twl_usb_comparator {
> usb-supply = <&vusb>;
> };
> +
> +&usb_otg_hs {
> + interface_type = <1>;
> + mode = <3>;
> + power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index c829d7e..5171739 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -542,5 +542,18 @@
> reg-names = "control_dev_conf", "otghs_control";
> ti,type = <1>;
> };
> +
> + usb_otg_hs: usb_otg_hs@4a0ab000 {
> + compatible = "ti,omap4-musb";
> + reg = <0x4a0ab000 0x7ff>;
> + 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>;
> + ti,has-mailbox;
> + };
> };
> };
> diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
> index ed0bc95..398d2c3 100644
> --- a/arch/arm/boot/dts/twl4030.dtsi
> +++ b/arch/arm/boot/dts/twl4030.dtsi
> @@ -67,7 +67,7 @@
> #interrupt-cells = <1>;
> };
>
> - twl4030-usb {
> + usb2_phy: twl4030-usb {
> compatible = "ti,twl4030-usb";
> interrupts = <10>, <4>;
> usb1v5-supply = <&vusb1v5>;
>
^ permalink raw reply [flat|nested] 33+ messages in thread* [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
@ 2013-02-07 6:21 ` Rajendra Nayak
0 siblings, 0 replies; 33+ messages in thread
From: Rajendra Nayak @ 2013-02-07 6:21 UTC (permalink / raw)
To: linux-arm-kernel
[]...
>
> 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 '_'
> + };
> };
> };
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index 4122efe..612c9bb 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -206,3 +206,9 @@
> &twl_usb_comparator {
> usb-supply = <&vusb>;
> };
> +
> +&usb_otg_hs {
> + interface_type = <1>;
> + mode = <3>;
> + power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 43e5258..582d7ee 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -428,3 +428,9 @@
> &twl_usb_comparator {
> usb-supply = <&vusb>;
> };
> +
> +&usb_otg_hs {
> + interface_type = <1>;
> + mode = <3>;
> + power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index c829d7e..5171739 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -542,5 +542,18 @@
> reg-names = "control_dev_conf", "otghs_control";
> ti,type = <1>;
> };
> +
> + usb_otg_hs: usb_otg_hs at 4a0ab000 {
> + compatible = "ti,omap4-musb";
> + reg = <0x4a0ab000 0x7ff>;
> + 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>;
> + ti,has-mailbox;
> + };
> };
> };
> diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
> index ed0bc95..398d2c3 100644
> --- a/arch/arm/boot/dts/twl4030.dtsi
> +++ b/arch/arm/boot/dts/twl4030.dtsi
> @@ -67,7 +67,7 @@
> #interrupt-cells = <1>;
> };
>
> - twl4030-usb {
> + usb2_phy: twl4030-usb {
> compatible = "ti,twl4030-usb";
> interrupts = <10>, <4>;
> usb1v5-supply = <&vusb1v5>;
>
^ permalink raw reply [flat|nested] 33+ messages in thread* Re: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
@ 2013-02-07 6:21 ` Rajendra Nayak
0 siblings, 0 replies; 33+ messages in thread
From: Rajendra Nayak @ 2013-02-07 6:21 UTC (permalink / raw)
To: Kishon Vijay Abraham I
Cc: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss, gregkh
[]...
>
> 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@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@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 '_'
> + };
> };
> };
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index 4122efe..612c9bb 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -206,3 +206,9 @@
> &twl_usb_comparator {
> usb-supply = <&vusb>;
> };
> +
> +&usb_otg_hs {
> + interface_type = <1>;
> + mode = <3>;
> + power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 43e5258..582d7ee 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -428,3 +428,9 @@
> &twl_usb_comparator {
> usb-supply = <&vusb>;
> };
> +
> +&usb_otg_hs {
> + interface_type = <1>;
> + mode = <3>;
> + power = <50>;
> +};
> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index c829d7e..5171739 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -542,5 +542,18 @@
> reg-names = "control_dev_conf", "otghs_control";
> ti,type = <1>;
> };
> +
> + usb_otg_hs: usb_otg_hs@4a0ab000 {
> + compatible = "ti,omap4-musb";
> + reg = <0x4a0ab000 0x7ff>;
> + 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>;
> + ti,has-mailbox;
> + };
> };
> };
> diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
> index ed0bc95..398d2c3 100644
> --- a/arch/arm/boot/dts/twl4030.dtsi
> +++ b/arch/arm/boot/dts/twl4030.dtsi
> @@ -67,7 +67,7 @@
> #interrupt-cells = <1>;
> };
>
> - twl4030-usb {
> + usb2_phy: twl4030-usb {
> compatible = "ti,twl4030-usb";
> interrupts = <10>, <4>;
> usb1v5-supply = <&vusb1v5>;
>
^ permalink raw reply [flat|nested] 33+ messages in thread* Re: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
2013-02-07 6:21 ` Rajendra Nayak
(?)
@ 2013-02-07 6:31 ` kishon
-1 siblings, 0 replies; 33+ messages in thread
From: kishon @ 2013-02-07 6:31 UTC (permalink / raw)
To: Rajendra Nayak
Cc: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss, gregkh
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@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@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
^ permalink raw reply [flat|nested] 33+ messages in thread* [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
@ 2013-02-07 6:31 ` kishon
0 siblings, 0 replies; 33+ messages in thread
From: kishon @ 2013-02-07 6:31 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 33+ messages in thread* Re: [PATCH 3/8] ARM: dts: omap: Add usb_otg and glue data
@ 2013-02-07 6:31 ` kishon
0 siblings, 0 replies; 33+ messages in thread
From: kishon @ 2013-02-07 6:31 UTC (permalink / raw)
To: Rajendra Nayak
Cc: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss, gregkh
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@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@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
^ permalink raw reply [flat|nested] 33+ messages in thread
* [PATCH 4/8] ARM: dts: omap5: Add omap control usb data
2013-02-06 14:56 ` Kishon Vijay Abraham I
(?)
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
-1 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 790bb2a..c937500 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -496,5 +496,13 @@
hw-caps-ll-interface;
hw-caps-temp-alert;
};
+
+ omap_control_usb: omap-control-usb@4a002300 {
+ compatible = "ti,omap-control-usb";
+ reg = <0x4a002300 0x4>,
+ <0x4a002370 0x4>;
+ reg-names = "control_dev_conf", "phy_power_usb";
+ ti,type = <2>;
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 4/8] ARM: dts: omap5: Add omap control usb data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 790bb2a..c937500 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -496,5 +496,13 @@
hw-caps-ll-interface;
hw-caps-temp-alert;
};
+
+ omap_control_usb: omap-control-usb at 4a002300 {
+ compatible = "ti,omap-control-usb";
+ reg = <0x4a002300 0x4>,
+ <0x4a002370 0x4>;
+ reg-names = "control_dev_conf", "phy_power_usb";
+ ti,type = <2>;
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 4/8] ARM: dts: omap5: Add omap control usb data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 790bb2a..c937500 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -496,5 +496,13 @@
hw-caps-ll-interface;
hw-caps-temp-alert;
};
+
+ omap_control_usb: omap-control-usb@4a002300 {
+ compatible = "ti,omap-control-usb";
+ reg = <0x4a002300 0x4>,
+ <0x4a002370 0x4>;
+ reg-names = "control_dev_conf", "phy_power_usb";
+ ti,type = <2>;
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread
* [PATCH 5/8] ARM: dts: omap5: Add ocp2scp data
2013-02-06 14:56 ` Kishon Vijay Abraham I
(?)
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
-1 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add ocp2scp data node in omap5 device tree file. The information for
the node added here can be found @
Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index c937500..230b779 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -504,5 +504,13 @@
reg-names = "control_dev_conf", "phy_power_usb";
ti,type = <2>;
};
+
+ ocp2scp {
+ compatible = "ti,omap-ocp2scp";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges;
+ ti,hwmods = "ocp2scp1";
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 5/8] ARM: dts: omap5: Add ocp2scp data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add ocp2scp data node in omap5 device tree file. The information for
the node added here can be found @
Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index c937500..230b779 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -504,5 +504,13 @@
reg-names = "control_dev_conf", "phy_power_usb";
ti,type = <2>;
};
+
+ ocp2scp {
+ compatible = "ti,omap-ocp2scp";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges;
+ ti,hwmods = "ocp2scp1";
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 5/8] ARM: dts: omap5: Add ocp2scp data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add ocp2scp data node in omap5 device tree file. The information for
the node added here can be found @
Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index c937500..230b779 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -504,5 +504,13 @@
reg-names = "control_dev_conf", "phy_power_usb";
ti,type = <2>;
};
+
+ ocp2scp {
+ compatible = "ti,omap-ocp2scp";
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges;
+ ti,hwmods = "ocp2scp1";
+ };
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread
* [PATCH 6/8] ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data
2013-02-06 14:56 ` Kishon Vijay Abraham I
(?)
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
-1 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 230b779..bd73257 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -511,6 +511,20 @@
#size-cells = <1>;
ranges;
ti,hwmods = "ocp2scp1";
+ usb2_phy: usb2phy@4a084000 {
+ compatible = "ti,omap-usb2";
+ reg = <0x4a084000 0x7c>;
+ ctrl-module = <&omap_control_usb>;
+ };
+
+ usb3_phy: usb3phy@4a084400 {
+ compatible = "ti,omap-usb3";
+ reg = <0x4a084400 0x80>,
+ <0x4a084800 0x64>,
+ <0x4a084c00 0x40>;
+ reg-names = "phy_rx", "phy_tx", "pll_ctrl";
+ ctrl-module = <&omap_control_usb>;
+ };
};
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 6/8] ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 230b779..bd73257 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -511,6 +511,20 @@
#size-cells = <1>;
ranges;
ti,hwmods = "ocp2scp1";
+ usb2_phy: usb2phy at 4a084000 {
+ compatible = "ti,omap-usb2";
+ reg = <0x4a084000 0x7c>;
+ ctrl-module = <&omap_control_usb>;
+ };
+
+ usb3_phy: usb3phy at 4a084400 {
+ compatible = "ti,omap-usb3";
+ reg = <0x4a084400 0x80>,
+ <0x4a084800 0x64>,
+ <0x4a084c00 0x40>;
+ reg-names = "phy_rx", "phy_tx", "pll_ctrl";
+ ctrl-module = <&omap_control_usb>;
+ };
};
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 6/8] ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 230b779..bd73257 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -511,6 +511,20 @@
#size-cells = <1>;
ranges;
ti,hwmods = "ocp2scp1";
+ usb2_phy: usb2phy@4a084000 {
+ compatible = "ti,omap-usb2";
+ reg = <0x4a084000 0x7c>;
+ ctrl-module = <&omap_control_usb>;
+ };
+
+ usb3_phy: usb3phy@4a084400 {
+ compatible = "ti,omap-usb3";
+ reg = <0x4a084400 0x80>,
+ <0x4a084800 0x64>,
+ <0x4a084c00 0x40>;
+ reg-names = "phy_rx", "phy_tx", "pll_ctrl";
+ ctrl-module = <&omap_control_usb>;
+ };
};
};
};
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread
* [PATCH 7/8] ARM: dts: omap5: add dwc3 omap dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index bd73257..c4eb2ec 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -505,6 +505,17 @@
ti,type = <2>;
};
+ omap_dwc3@4a020000 {
+ compatible = "ti,dwc3";
+ ti,hwmods = "usb_otg_ss";
+ reg = <0x4a020000 0x1000>;
+ interrupts = <0 93 4>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ utmi-mode = <2>;
+ ranges;
+ };
+
ocp2scp {
compatible = "ti,omap-ocp2scp";
#address-cells = <1>;
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 7/8] ARM: dts: omap5: add dwc3 omap dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index bd73257..c4eb2ec 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -505,6 +505,17 @@
ti,type = <2>;
};
+ omap_dwc3 at 4a020000 {
+ compatible = "ti,dwc3";
+ ti,hwmods = "usb_otg_ss";
+ reg = <0x4a020000 0x1000>;
+ interrupts = <0 93 4>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ utmi-mode = <2>;
+ ranges;
+ };
+
ocp2scp {
compatible = "ti,omap-ocp2scp";
#address-cells = <1>;
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 7/8] ARM: dts: omap5: add dwc3 omap dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson-l0cyMroinI0, tony-4v6yS6AI5VpBDgjK7y7TUQ,
linux-lFZ/pmaqli7XmaaqVzeoHQ, rob.herring-bsGFqQB8/DxBDgjK7y7TUQ,
rob-VoJi6FS/r0vR7s880joybQ, balbi-l0cyMroinI0,
linux-usb-u79uwXL29TY76Z2rM5mHXA,
linux-omap-u79uwXL29TY76Z2rM5mHXA,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
linux-doc-u79uwXL29TY76Z2rM5mHXA,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r, kishon-l0cyMroinI0
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I <kishon-l0cyMroinI0@public.gmane.org>
---
arch/arm/boot/dts/omap5.dtsi | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index bd73257..c4eb2ec 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -505,6 +505,17 @@
ti,type = <2>;
};
+ omap_dwc3@4a020000 {
+ compatible = "ti,dwc3";
+ ti,hwmods = "usb_otg_ss";
+ reg = <0x4a020000 0x1000>;
+ interrupts = <0 93 4>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ utmi-mode = <2>;
+ ranges;
+ };
+
ocp2scp {
compatible = "ti,omap-ocp2scp";
#address-cells = <1>;
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread
* [PATCH 8/8] ARM: dts: omap5: add dwc3 core dt data
2013-02-06 14:56 ` Kishon Vijay Abraham I
(?)
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
-1 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
Documentation/devicetree/bindings/usb/dwc3.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index c4eb2ec..24dd69f 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -514,6 +514,13 @@
#size-cells = <1>;
utmi-mode = <2>;
ranges;
+ dwc3@4a030000 {
+ compatible = "synopsys,dwc3";
+ reg = <0x4a030000 0x1000>;
+ interrupts = <0 92 4>;
+ usb-phy = <&usb2_phy>, <&usb3_phy>;
+ tx-fifo-resize;
+ };
};
ocp2scp {
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 8/8] ARM: dts: omap5: add dwc3 core dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: linux-arm-kernel
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
Documentation/devicetree/bindings/usb/dwc3.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index c4eb2ec..24dd69f 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -514,6 +514,13 @@
#size-cells = <1>;
utmi-mode = <2>;
ranges;
+ dwc3 at 4a030000 {
+ compatible = "synopsys,dwc3";
+ reg = <0x4a030000 0x1000>;
+ interrupts = <0 92 4>;
+ usb-phy = <&usb2_phy>, <&usb3_phy>;
+ tx-fifo-resize;
+ };
};
ocp2scp {
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread* [PATCH 8/8] ARM: dts: omap5: add dwc3 core dt data
@ 2013-02-06 14:56 ` Kishon Vijay Abraham I
0 siblings, 0 replies; 33+ messages in thread
From: Kishon Vijay Abraham I @ 2013-02-06 14:56 UTC (permalink / raw)
To: b-cousson, tony, linux, rob.herring, rob, balbi, linux-usb,
linux-omap, linux-kernel, linux-doc, linux-arm-kernel,
devicetree-discuss
Cc: grant.likely, gregkh, kishon
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
Documentation/devicetree/bindings/usb/dwc3.txt
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/omap5.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index c4eb2ec..24dd69f 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -514,6 +514,13 @@
#size-cells = <1>;
utmi-mode = <2>;
ranges;
+ dwc3@4a030000 {
+ compatible = "synopsys,dwc3";
+ reg = <0x4a030000 0x1000>;
+ interrupts = <0 92 4>;
+ usb-phy = <&usb2_phy>, <&usb3_phy>;
+ tx-fifo-resize;
+ };
};
ocp2scp {
--
1.7.10.4
^ permalink raw reply related [flat|nested] 33+ messages in thread