mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
8934d3e4d0
omap_get_control_dev() is being deprecated as it doesn't support multiple instances. As control device is present only from OMAP4 onwards which supports DT only, we use phandles to get the reference to the control device. Also get rid of "ti,has-mailbox" property as it is redundant and we can determine that from whether "ctrl-module" property is present or not. Get rid of has_mailbox from musb_hdrc_platform_data as well. Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
101 lines
3.4 KiB
Plaintext
101 lines
3.4 KiB
Plaintext
OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS
|
|
|
|
OMAP MUSB GLUE
|
|
- compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
|
|
- ti,hwmods : must be "usb_otg_hs"
|
|
- multipoint : Should be "1" indicating the musb controller supports
|
|
multipoint. This is a MUSB configuration-specific setting.
|
|
- num-eps : Specifies the number of endpoints. This is also a
|
|
MUSB configuration-specific setting. Should be set to "16"
|
|
- ram-bits : Specifies the ram address size. Should be set to "12"
|
|
- interface-type : This is a board specific setting to describe the type of
|
|
interface between the controller and the phy. It should be "0" or "1"
|
|
specifying ULPI and UTMI respectively.
|
|
- mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
|
|
represents PERIPHERAL.
|
|
- power : Should be "50". This signifies the controller can supply up to
|
|
100mA when operating in host mode.
|
|
- usb-phy : the phandle for the PHY device
|
|
- phys : the phandle for the PHY device (used by generic PHY framework)
|
|
- phy-names : the names of the PHY corresponding to the PHYs present in the
|
|
*phy* phandle.
|
|
|
|
Optional properties:
|
|
- ctrl-module : phandle of the control module this glue uses to write to
|
|
mailbox
|
|
|
|
SOC specific device node entry
|
|
usb_otg_hs: usb_otg_hs@4a0ab000 {
|
|
compatible = "ti,omap4-musb";
|
|
ti,hwmods = "usb_otg_hs";
|
|
multipoint = <1>;
|
|
num-eps = <16>;
|
|
ram-bits = <12>;
|
|
ctrl-module = <&omap_control_usb>;
|
|
phys = <&usb2_phy>;
|
|
phy-names = "usb2-phy";
|
|
};
|
|
|
|
Board specific device node entry
|
|
&usb_otg_hs {
|
|
interface-type = <1>;
|
|
mode = <3>;
|
|
power = <50>;
|
|
};
|
|
|
|
OMAP DWC3 GLUE
|
|
- compatible : Should be "ti,dwc3"
|
|
- ti,hwmods : Should be "usb_otg_ss"
|
|
- reg : Address and length of the register set for the device.
|
|
- interrupts : The irq number of this device that is used to interrupt the
|
|
MPU
|
|
- #address-cells, #size-cells : Must be present if the device has sub-nodes
|
|
- utmi-mode : controls the source of UTMI/PIPE status for VBUS and OTG ID.
|
|
It should be set to "1" for HW mode and "2" for SW mode.
|
|
- ranges: the child address space are mapped 1:1 onto the parent address space
|
|
|
|
Optional Properties:
|
|
- extcon : phandle for the extcon device omap dwc3 uses to detect
|
|
connect/disconnect events.
|
|
- vbus-supply : phandle to the regulator device tree node if needed.
|
|
|
|
Sub-nodes:
|
|
The dwc3 core should be added as subnode to omap dwc3 glue.
|
|
- dwc3 :
|
|
The binding details of dwc3 can be found in:
|
|
Documentation/devicetree/bindings/usb/dwc3.txt
|
|
|
|
omap_dwc3 {
|
|
compatible = "ti,dwc3";
|
|
ti,hwmods = "usb_otg_ss";
|
|
reg = <0x4a020000 0x1ff>;
|
|
interrupts = <0 93 4>;
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
utmi-mode = <2>;
|
|
ranges;
|
|
};
|
|
|
|
OMAP CONTROL USB
|
|
|
|
Required properties:
|
|
- compatible: Should be one of
|
|
"ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
|
|
"ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
|
|
e.g. USB2_PHY on OMAP5.
|
|
"ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control
|
|
e.g. USB3 PHY and SATA PHY on OMAP5.
|
|
"ti,control-phy-dra7usb2" - if it has power down register like USB2 PHY on
|
|
DRA7 platform.
|
|
- reg : Address and length of the register set for the device. It contains
|
|
the address of "otghs_control" for control-phy-otghs or "power" register
|
|
for other types.
|
|
- reg-names: should be "otghs_control" control-phy-otghs and "power" for
|
|
other types.
|
|
|
|
omap_control_usb: omap-control-usb@4a002300 {
|
|
compatible = "ti,control-phy-otghs";
|
|
reg = <0x4a00233c 0x4>;
|
|
reg-names = "otghs_control";
|
|
};
|