blob: 1ef0ce71f8faa0f00bb0e459c7c94a36d6abdb1b [file] [log] [blame]
Kishon Vijay Abraham I01658f02013-01-25 15:53:57 +05301OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS
Kishon Vijay Abraham I00a0b1d2012-09-11 14:39:40 +05302
3OMAP MUSB GLUE
4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
5 - ti,hwmods : must be "usb_otg_hs"
Kishon Vijay Abraham Ica784be2013-01-25 15:54:00 +05306 - 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.
Kishon Vijay Abraham I00a0b1d2012-09-11 14:39:40 +05309 - multipoint : Should be "1" indicating the musb controller supports
10 multipoint. This is a MUSB configuration-specific setting.
11 - num_eps : Specifies the number of endpoints. This is also a
12 MUSB configuration-specific setting. Should be set to "16"
13 - ram_bits : Specifies the ram address size. Should be set to "12"
14 - interface_type : This is a board specific setting to describe the type of
15 interface between the controller and the phy. It should be "0" or "1"
16 specifying ULPI and UTMI respectively.
17 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
18 represents PERIPHERAL.
19 - power : Should be "50". This signifies the controller can supply upto
20 100mA when operating in host mode.
21
Kishon Vijay Abraham I01658f02013-01-25 15:53:57 +053022Optional properties:
23 - ctrl-module : phandle of the control module this glue uses to write to
24 mailbox
25
Kishon Vijay Abraham I00a0b1d2012-09-11 14:39:40 +053026SOC specific device node entry
27usb_otg_hs: usb_otg_hs@4a0ab000 {
28 compatible = "ti,omap4-musb";
29 ti,hwmods = "usb_otg_hs";
Kishon Vijay Abraham Ica784be2013-01-25 15:54:00 +053030 ti,has-mailbox;
Kishon Vijay Abraham I00a0b1d2012-09-11 14:39:40 +053031 multipoint = <1>;
32 num_eps = <16>;
33 ram_bits = <12>;
Kishon Vijay Abraham I01658f02013-01-25 15:53:57 +053034 ctrl-module = <&omap_control_usb>;
Kishon Vijay Abraham I00a0b1d2012-09-11 14:39:40 +053035};
36
37Board specific device node entry
38&usb_otg_hs {
39 interface_type = <1>;
40 mode = <3>;
41 power = <50>;
42};
Kishon Vijay Abraham I01658f02013-01-25 15:53:57 +053043
44OMAP CONTROL USB
45
46Required properties:
47 - compatible: Should be "ti,omap-control-usb"
48 - reg : Address and length of the register set for the device. It contains
49 the address of "control_dev_conf" and "otghs_control" or "phy_power_usb"
50 depending upon omap4 or omap5.
51 - reg-names: The names of the register addresses corresponding to the registers
52 filled in "reg".
53 - ti,type: This is used to differentiate whether the control module has
54 usb mailbox or usb3 phy power. omap4 has usb mailbox in control module to
55 notify events to the musb core and omap5 has usb3 phy power register to
56 power on usb3 phy. Should be "1" if it has mailbox and "2" if it has usb3
57 phy power.
58
59omap_control_usb: omap-control-usb@4a002300 {
60 compatible = "ti,omap-control-usb";
61 reg = <0x4a002300 0x4>,
62 <0x4a00233c 0x4>;
63 reg-names = "control_dev_conf", "otghs_control";
64 ti,type = <1>;
65};