Change D-PHY lanes v4l2 can't received data

Hi everyone,

I’m working on Xavier, JetPack 4.4, L4T R32.4.3.
When I test D-PHY signal by using different lanes(1/2/3/4), only Lane 2 is work on V4l2.

The Device Tree just change 2 parameter:num_lanes and bus-width
Here’s my device tree which is D-PHYx1Lane

mode0 { // OV5693_MODE_2592X1944
				mclk_khz = "37125";//?
				num_lanes = "1";//?
				tegra_sinterface = "serial_e";//?
				phy_mode = "DPHY";//?
				discontinuous_clk = "no";//?
				dpcm_enable = "false";//?
				cil_settletime = "0";//?

				active_w = "4928";//
				active_h = "5000";//
				mode_type = "bayer";
				pixel_phase = "rggb";//?
 				//dynamic_pixel_bit_depth = "12";
				csi_pixel_bit_depth = "12";//The sensor readout pixel pattern
				readout_orientation = "0";//
				line_length = "5000";//
				inherent_gain = "1";//
				mclk_multiplier = "2";//
				pix_clk_hz = "74250000";//

				gain_factor = "10";
				min_gain_val = "0";//
				max_gain_val = "720";//
				step_gain_val = "3";
				default_gain = "0";
				min_hdr_ratio = "1";//
				max_hdr_ratio = "1";//
				framerate_factor = "1000000";
				min_framerate = "2000000";//
				max_framerate = "30000000";//
				step_framerate = "1";
				default_framerate = "30000000";
				exposure_factor = "1000000";
				min_exp_time = "30";//
				max_exp_time = "660000";//
				step_exp_time = "1";
				default_exp_time = "33334";
				embedded_metadata_height = "0";//?
			};

			ports {
				#address-cells = <1>;
				#size-cells = <0>;

				port@0 {
					reg = <0>;
					e3326_ov5693_out0: endpoint {
						port-index = <4>;
						bus-width = <1>;
						remote-endpoint = <&e3326_csi_in0>;
					};
				};
			};

Also, I use gst command double check that.
And gst can work!

Below is dmesg

[  572.999420] t194-nvcsi 15a00000.nvcsi: csi5_mipi_cal,phy_mode = 0, csi5_fops.c
[  572.999429] csi5_phy_write, csi5_fops.c:52
[  573.050205] [RCE] vi5_hwinit: firmware CL2018101701 protocol version 2.2
[  573.057146] t194-nvcsi 15a00000.nvcsi: csi5_stream_set_config: stream_id=4, csi_port=4,phy_mode = 0, csi5_fops.c:147
[  573.057161] t194-nvcsi 15a00000.nvcsi: csi5_stream_open: stream_id=4, csi_port=4, csi5_fops.c:94
[  575.573755] tegra194-vi5 15c10000.vi: no reply from camera processor
[  575.573921] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[  575.574073] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[  575.575926] t194-nvcsi 15a00000.nvcsi: csi5_stream_set_config: stream_id=4, csi_port=4,phy_mode = 0, csi5_fops.c:147
[  575.575938] t194-nvcsi 15a00000.nvcsi: csi5_stream_open: stream_id=4, csi_port=4, csi5_fops.c:94
[  575.576178] tegra-capture-ivc ivc-bc00000.rtcpu:ivccontrol@3: No callback found for msg id: 0x37
[  575.576386] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[  578.389385] tegra194-vi5 15c10000.vi: no reply from camera processor
[  578.389580] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[  578.389722] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[  578.392397] t194-nvcsi 15a00000.nvcsi: csi5_stream_set_config: stream_id=4, csi_port=4,phy_mode = 0, csi5_fops.c:147
[  578.392409] t194-nvcsi 15a00000.nvcsi: csi5_stream_open: stream_id=4, csi_port=4, csi5_fops.c:94
[  578.392744] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[  581.460849] tegra194-vi5 15c10000.vi: no reply from camera processor
[  581.461050] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[  581.461204] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[  581.463433] t194-nvcsi 15a00000.nvcsi: csi5_stream_set_config: stream_id=4, csi_port=4,phy_mode = 0, csi5_fops.c:147
[  581.463445] t194-nvcsi 15a00000.nvcsi: csi5_stream_open: stream_id=4, csi_port=4, csi5_fops.c:94
[  581.463774] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[  584.276512] tegra194-vi5 15c10000.vi: no reply from camera processor
[  584.276706] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[  584.276866] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel

Did you modify sensor REG for corresponding lane configure.
Also suppose there’s no 3 lanes support.

Thanks for reply.
Yes. I’m not using REAL camera but another device to generate MIPI signal.
And it can set different lane.

You check the trace log to check the root cause.

https://elinux.org/Jetson/l4t/Camera_BringUp

Hi Shane,
Does AGX Xavier support D-PHY x 3Lane?

Don’t support DPHY 3 lanes configure.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.