1 OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS
4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
5 - ti,hwmods : must be "usb_otg_hs"
6 - multipoint : Should be "1" indicating the musb controller supports
7 multipoint. This is a MUSB configuration-specific setting.
8 - num_eps : Specifies the number of endpoints. This is also a
9 MUSB configuration-specific setting. Should be set to "16"
10 - ram_bits : Specifies the ram address size. Should be set to "12"
11 - interface_type : This is a board specific setting to describe the type of
12 interface between the controller and the phy. It should be "0" or "1"
13 specifying ULPI and UTMI respectively.
14 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
15 represents PERIPHERAL.
16 - power : Should be "50". This signifies the controller can supply upto
17 100mA when operating in host mode.
20 - ctrl-module : phandle of the control module this glue uses to write to
23 SOC specific device node entry
24 usb_otg_hs: usb_otg_hs@4a0ab000 {
25 compatible = "ti,omap4-musb";
26 ti,hwmods = "usb_otg_hs";
30 ctrl-module = <&omap_control_usb>;
33 Board specific device node entry
43 - compatible: Should be "ti,omap-control-usb"
44 - reg : Address and length of the register set for the device. It contains
45 the address of "control_dev_conf" and "otghs_control" or "phy_power_usb"
46 depending upon omap4 or omap5.
47 - reg-names: The names of the register addresses corresponding to the registers
49 - ti,type: This is used to differentiate whether the control module has
50 usb mailbox or usb3 phy power. omap4 has usb mailbox in control module to
51 notify events to the musb core and omap5 has usb3 phy power register to
52 power on usb3 phy. Should be "1" if it has mailbox and "2" if it has usb3
55 omap_control_usb: omap-control-usb@4a002300 {
56 compatible = "ti,omap-control-usb";
57 reg = <0x4a002300 0x4>,
59 reg-names = "control_dev_conf", "otghs_control";