Platform Adaptation and Bring-Up
Jetson Nano Platform Adaptation and Bring-Up Guide DA_09361-002 | 15
pcie {
status = "okay";
lanes { ...//UPHY lane assignment
};
};
};
ports {
usb2-1 {
mode = "host";
vbus-supply = <&battery_reg>;
status = "okay";
};
...
usb3-0 {
nvidia,usb2-companion = <1>;
status = "okay";
};
...
};
};
Under the xusb Node
The Jetson Nano xHCI controller complies with xHCI specifications, which support both
USB 2.0 HighSpeed/FullSpeed/LowSpeed and USB 3.0 SuperSpeed protocols.
• phys
Must contain an entry for each entry in phy-names.
• phy-names
Must include an entry for each PHY used by the controller. Names must be of the
form <type>-<port_number>, where <type> is "usb2" or "usb3".
• nvidia,boost_cpu_freq
Set the value to which CPU frequency will be boosted. This is only the minimum
frequency, DVFS can scale up CPU frequency further based on need and CPU
loading. CPU boost frequency through PMQOS is enabled for the xHCI controller
only when this field’s is greater than zero. The boost is applicable only for bulk and
ISOC transfers; other endpoints do not need to be boosted.
• nvidia,boost_cpu_trigger
Minimum buffer length of the bulk or ISOC transfers beyond which to boost
frequency.
• nvidia,xusb-padctl
A pointer to the xusb-padctl node.
For the detailed information about xHCI, see the documentation at: