1 OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS 1 OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS
2 2
3 OMAP MUSB GLUE 3 OMAP MUSB GLUE
4 - compatible : Should be "ti,omap4-musb" or " 4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
5 - ti,hwmods : must be "usb_otg_hs" 5 - ti,hwmods : must be "usb_otg_hs"
>> 6 - ti,has-mailbox : to specify that omap uses an external mailbox
>> 7 (in control module) to communicate with the musb core during device connect
>> 8 and disconnect.
6 - multipoint : Should be "1" indicating the m 9 - multipoint : Should be "1" indicating the musb controller supports
7 multipoint. This is a MUSB configuration-sp 10 multipoint. This is a MUSB configuration-specific setting.
8 - num-eps : Specifies the number of endpoints 11 - num-eps : Specifies the number of endpoints. This is also a
9 MUSB configuration-specific setting. Should 12 MUSB configuration-specific setting. Should be set to "16"
10 - ram-bits : Specifies the ram address size. 13 - ram-bits : Specifies the ram address size. Should be set to "12"
11 - interface-type : This is a board specific s 14 - interface-type : This is a board specific setting to describe the type of
12 interface between the controller and the ph 15 interface between the controller and the phy. It should be "0" or "1"
13 specifying ULPI and UTMI respectively. 16 specifying ULPI and UTMI respectively.
14 - mode : Should be "3" to represent OTG. "1" 17 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
15 represents PERIPHERAL. 18 represents PERIPHERAL.
16 - power : Should be "50". This signifies the !! 19 - power : Should be "50". This signifies the controller can supply upto
17 100mA when operating in host mode. 20 100mA when operating in host mode.
18 - usb-phy : the phandle for the PHY device 21 - usb-phy : the phandle for the PHY device
19 - phys : the phandle for the PHY device (used <<
20 - phy-names : the names of the PHY correspond <<
21 *phy* phandle. <<
22 22
23 Optional properties: 23 Optional properties:
24 - ctrl-module : phandle of the control module 24 - ctrl-module : phandle of the control module this glue uses to write to
25 mailbox 25 mailbox
26 26
27 SOC specific device node entry 27 SOC specific device node entry
28 usb_otg_hs: usb_otg_hs@4a0ab000 { 28 usb_otg_hs: usb_otg_hs@4a0ab000 {
29 compatible = "ti,omap4-musb"; 29 compatible = "ti,omap4-musb";
30 ti,hwmods = "usb_otg_hs"; 30 ti,hwmods = "usb_otg_hs";
>> 31 ti,has-mailbox;
31 multipoint = <1>; 32 multipoint = <1>;
32 num-eps = <16>; 33 num-eps = <16>;
33 ram-bits = <12>; 34 ram-bits = <12>;
34 ctrl-module = <&omap_control_usb>; 35 ctrl-module = <&omap_control_usb>;
35 phys = <&usb2_phy>; <<
36 phy-names = "usb2-phy"; <<
37 }; 36 };
38 37
39 Board specific device node entry 38 Board specific device node entry
40 &usb_otg_hs { 39 &usb_otg_hs {
41 interface-type = <1>; 40 interface-type = <1>;
42 mode = <3>; 41 mode = <3>;
43 power = <50>; 42 power = <50>;
44 }; 43 };
45 44
46 OMAP DWC3 GLUE 45 OMAP DWC3 GLUE
47 - compatible : Should be !! 46 - compatible : Should be "ti,dwc3"
48 * "ti,dwc3" for OMAP5 and DRA7 <<
49 * "ti,am437x-dwc3" for AM437x <<
50 - ti,hwmods : Should be "usb_otg_ss" 47 - ti,hwmods : Should be "usb_otg_ss"
51 - reg : Address and length of the register se 48 - reg : Address and length of the register set for the device.
52 - interrupts : The irq number of this device 49 - interrupts : The irq number of this device that is used to interrupt the
53 MPU 50 MPU
54 - #address-cells, #size-cells : Must be prese 51 - #address-cells, #size-cells : Must be present if the device has sub-nodes
55 - utmi-mode : controls the source of UTMI/PIP 52 - utmi-mode : controls the source of UTMI/PIPE status for VBUS and OTG ID.
56 It should be set to "1" for HW mode and "2" 53 It should be set to "1" for HW mode and "2" for SW mode.
57 - ranges: the child address space are mapped 54 - ranges: the child address space are mapped 1:1 onto the parent address space
58 55
59 Optional Properties: <<
60 - extcon : phandle for the extcon device omap <<
61 connect/disconnect events. <<
62 - vbus-supply : phandle to the regulator devi <<
63 <<
64 Sub-nodes: 56 Sub-nodes:
65 The dwc3 core should be added as subnode to om 57 The dwc3 core should be added as subnode to omap dwc3 glue.
66 - dwc3 : 58 - dwc3 :
67 The binding details of dwc3 can be found in 59 The binding details of dwc3 can be found in:
68 Documentation/devicetree/bindings/usb/snps, !! 60 Documentation/devicetree/bindings/usb/dwc3.txt
69 61
70 omap_dwc3 { 62 omap_dwc3 {
71 compatible = "ti,dwc3"; 63 compatible = "ti,dwc3";
72 ti,hwmods = "usb_otg_ss"; 64 ti,hwmods = "usb_otg_ss";
73 reg = <0x4a020000 0x1ff>; 65 reg = <0x4a020000 0x1ff>;
74 interrupts = <0 93 4>; 66 interrupts = <0 93 4>;
75 #address-cells = <1>; 67 #address-cells = <1>;
76 #size-cells = <1>; 68 #size-cells = <1>;
77 utmi-mode = <2>; 69 utmi-mode = <2>;
78 ranges; 70 ranges;
79 }; 71 };
80 72
>> 73 OMAP CONTROL USB
>> 74
>> 75 Required properties:
>> 76 - compatible: Should be "ti,omap-control-usb"
>> 77 - reg : Address and length of the register set for the device. It contains
>> 78 the address of "control_dev_conf" and "otghs_control" or "phy_power_usb"
>> 79 depending upon omap4 or omap5.
>> 80 - reg-names: The names of the register addresses corresponding to the registers
>> 81 filled in "reg".
>> 82 - ti,type: This is used to differentiate whether the control module has
>> 83 usb mailbox or usb3 phy power. omap4 has usb mailbox in control module to
>> 84 notify events to the musb core and omap5 has usb3 phy power register to
>> 85 power on usb3 phy. Should be "1" if it has mailbox and "2" if it has usb3
>> 86 phy power.
>> 87
>> 88 omap_control_usb: omap-control-usb@4a002300 {
>> 89 compatible = "ti,omap-control-usb";
>> 90 reg = <0x4a002300 0x4>,
>> 91 <0x4a00233c 0x4>;
>> 92 reg-names = "control_dev_conf", "otghs_control";
>> 93 ti,type = <1>;
>> 94 };
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.