Platform Adaptation and Bring-Up
Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 23
Number of cells in the extcon specifier. Must be 1.
For the example of J28, the USB2.0 Micro B connector, create an xHCI node and property
list based on the device tree structure described in Under the extcon Node
for a host-
only port, plus the additional settings above:
xusb@70090000 {
...
extcon-cables = <&vbus_id_gpio_extcon 1>;
extcon-cable-names = "id";
#extcon-cells = <1>;
phys = <&{/xusb_padctl@7009f000/pads/usb2/lanes/usb2-0}>;
phy-names = "usb2-0";
nvidia,xusb-padctl = <&xusb_padctl>;
status = "okay";
...
};
Under the xUDC Node
The Jetson Nano xUDC controller supports both USB 2.0 HighSpeed/FullSpeed and USB
3.0 SuperSpeed protocols.
These are the device tree node properties that apply to the xUDC node:
• extcon-cables
OTG support. Must contains an extcon-cable entry that detects the USB VBUS
pin. When the extcon cable state is 1, OTG port transitions to the device role.
• extcon-cable-names
Must be vbus.
• charger-detector
USB charger detection support. Must be the phandle of the USB charger detection
driver DT node.
• phys
An array; must contain pointers to the nodes that define each PHY in phy-names.
• phy-names
An array; must contain an entry for each PHY used by the controller. Names must be
in the form <type>-<port_number>, where <type> is usb2 or usb3.
• nvidia,boost_cpu_freq
The value to which CPU frequency is to be boosted. This is only the minimum
frequency; DVFS can scale up CPU frequency further based on need and CPU load.
CPU boost frequency through PMQOS is enabled for the xUDC controller only when
To Next Page
Loading...
Need help?
General
