Jetson-AGX-ORIN add FUSB301

now, i’m trying to connect JAO to FUSB301, how to do for l4t

refer to Orin Nano devkit device tree.

1 Like

thinks for your reply !
The translation of your preliminary exploration conclusions into English is as follows:

  1. The system source code for JAO and JON is consistent, so the FUSB301 driver source code is available in both. This means that the driver source code and its configuration are the same.
  2. Based on the previous point, I understand that I only need to configure the I2C device tree file that connects JAO and FUSB301.
  3. In the device tree file, the pinmux configuration file can use the default settings. Is it sufficient to place the following code from JON in the appropriate position?

Please note that the actual placement of the device tree snippet within the overall device tree for your system will depend on the specific configuration of your Jetson device. You should ensure that the fusb301 node is included in the appropriate place within the device tree hierarchy for your system to function correctly.

i2c@c240000 {
	status = "okay";
	fusb301@25 {
		compatible = "onsemi,fusb301";
		reg = <0x25>;
		status = "okay";
		#address-cells = <1>;
		#size-cells = <0>;
		interrupt-parent = <&tegra_main_gpio>;
		interrupts = <TEGRA234_MAIN_GPIO(Z, 1) IRQ_TYPE_LEVEL_LOW>;
		connector@0 {
			port@0 {
				fusb_p0: endpoint {
					remote-endpoint = <&typec_p0>;

Side note, I want to delve deeper into the entire L4T source code system and the structure of the flashing files, how do I go about it?

This is because every time I adapt the Jetson to my baseboard, when I encounter special requirements, I always can’t find the answers in the official documentation.

Can I place this code in /ssd/nvme1n1p4/nvidia_sdk/JAO/JAO_L4T3531_sources_rev_D/kernel_file/Linux_for_Tegra/source/public/hardware/nvidia/platform/t23x/concord/kernel-dts/cvb/tegra234-p3737-0000-a04.dtsi ?