The memory address contains three pieces that is the reset module which
is currently the only one used and two other pices which seem
interresting based on what the register.
The phy id (0 or 1) can be obtained via of_alias_get_id(). However once
we need this, we should used something for common register access.
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
---
arch/arm/boot/dts/am33xx.dtsi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 0d4df90..a24f1cb 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -333,6 +333,22 @@
status = "disabled";
};
+ musb0_phy: phy0@47401000 {
+ compatible = "ti,am335x-usb-phy";
+ reg = <0x44e10620 0x2c /* reset module */
+ 0x47401000 0x200
+ 0x47401300 0x100>;
+ status = "disabled";
+ };
+
+ musb1_phy: phy1@47401800 {
+ compatible = "ti,am335x-usb-phy";
+ reg = <0x44e10628 0x24 /* reset module */
+ 0x47401800 0x200
+ 0x47401b00 0x100>;
+ status = "disabled";
+ };
+
usb@47400000 {
compatible = "ti,musb-am33xx";
reg = <0x47400000 0x1000 /* usbss */
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
