Meaning of the CSI lane alignment error

Hello!
We use a proprietary camera providing a 4-lane MIPI-CSI interface with a custom carrier board.
After adapting the manufacturer’s suggested configuration for the TX2, we observed that the capture does not function, producing various CIL errors. After configuring the pixel clock and the cil_settletime parameters, a new kind of error, seemingly not described before, can be seen.

     kworker/3:4-100     [003] ....   144.979436: rtcpu_nvcsi_intr: tstamp:5095728260 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x10000000
     kworker/3:4-100     [003] ....   144.979436: rtcpu_nvcsi_intr: tstamp:5095728260 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000004

According to the TRM, those status values correspond to intr_dphy_cil_lane_align_err_a and intr_cil_data_lane_sot_mb_err0_a.
However, no description is provided as to what the lane alignment error actually means.

Any information to shed light on this issue would be very welcome.

For reference, here is a snippet of the device tree sources.

mode0 {
	//mclk_khz = "200000";
	//mclk_multiplier = "1";

	num_lanes = "4";
	tegra_sinterface = "serial_c";
	phy_mode = "DPHY";
	discontinuous_clk = "no"; // continuous clock
	dpcm_enable = "false";

	cil_settletime = "30";

	active_w = "1280";
	active_h = "512";

	pixel_t = "gray";
	csi_pixel_bit_depth = "8";

	readout_orientation = "0";

	line_length = "1280";
	inherent_gain = "1";

	// https://docs.nvidia.com/jetson/archives/r35.1/DeveloperGuide/text/SD/CameraDevelopment/SensorSoftwareDriverProgramming.html#sensor-pixel-clock
	// 400 Mbps (200 MHz DDR clock) * 4 lanes / 8 bpp = 200 MHz
	// pix_clk_hz = "200000000";
	pix_clk_hz = "200000000";

	gain_factor = "10";
	min_gain_val = "10";/* 1DB*/
	max_gain_val = "160";/* 16DB*/
	step_gain_val = "1";
	default_gain = "10";
	min_hdr_ratio = "1";
	max_hdr_ratio = "1";
	framerate_factor = "1000000";
	min_framerate = "30000000";/*30*/
	max_framerate = "60000000";/*30*/
	step_framerate = "1";
	default_framerate = "30000000";
	exposure_factor = "1000000";
	min_exp_time = "30";/* us */
	max_exp_time = "660000";/* us */
	step_exp_time = "1";
	default_exp_time = "33333";/* us */

	embedded_metadata_height = "1";
};

It tell some lane detect 0xFF sync word(deskew word), while others not

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