CSI dual 4lane configuration

Hi,

Does Orin NX support dual 4lanes sensor? Understand the dev kit hardware is only 2lane + 4lanes, I’m thinking it on customed board.
For the tegra234-p3767-camera-p3768-imx477-dual-4lane.dts, it looks like it’s just 4 + 2 lanes.

			tegra-capture-vi  {
				num-channels = <2>;
				ports {
					#address-cells = <1>;
					#size-cells = <0>;
					port@0 {
						reg = <0>;
						rbpcv3_imx477_vi_in0: endpoint {
							port-index = <1>;
							bus-width = <4>;
							remote-endpoint = <&rbpcv3_imx477_csi_out0>;
						};
					};
					port@1 {
						reg = <1>;
						rbpcv3_imx477_vi_in1: endpoint {
							port-index = <2>;
							bus-width = <2>;
							remote-endpoint = <&rbpcv3_imx477_csi_out1>;
						};
					};
				};
			};

Orin NX/Nano devkit only cam1(csi-c) able support 4 lanes configuration.
CAM0 only support 2 lanes.

Thanks

Hi Shane,
Thanks. Unstand the devkit only support 4+2 lanes. I’m thinking it on customed board.
To implement below 4 +4 configuration. I just need to change port-index and bus-width based on tegra234-p3767-camera-p3768-imx477-dual-4lane.dts, is it corret, is it correct?

Yes, it’s correct. BTW, need lane_polarity=“6”; in CSI-A/B

Thanks ShaneCCC! In the default file tegra234-p3767-camera-p3768-imx477-dual-4lane.dts, there are 4 lane_polarity. line 285, 323, 395, 433. The first two lane_polarity = “6”, the later two lane_polarity = “0”.
Comparing the video0 and video1 setting, looks like not just change lane_polarity.

Hi @zt_minto
The other changes you can see in the device-tree are there because the num-lanes is increased from 2 → 4.
That makes it necessary to update the speed at which the camera is expected to send data. If the pix_clk_hz stays the same, the frames would be rejected or become corrupted when received.

Other changes are just related to keeping the camera port on which the camera is connected.

Embedded SW Engineer at RidgeRun

Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com

Hi jafeth, thanks for the explanaiton