HDMI input issue with lt6911 bridge chip on jetson TX2 nx custom board

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

The boards I use are jetson tx2 nx core board and custom carrier board. I refer url link Device Tree for CSI MIPI to modify the device tree file and enable the lt6911 driver. I connect my windows PC HDMI ouput to my jetson tx2 nx board HDMI input, but I cannot capture the video streaming using the v4l2 tools.
The ouputs are given as follows:

~$dmesg |grep lt6911
[    1.334753] lt6911uxc 9-0010: probing lt6911uxc v4l2 sensor at addr 0x10
[    1.341607] lt6911uxc 9-0010: mclk absent,assuming sensor driven externally
[    1.348740] lt6911uxc 9-0010: tegracam sensor driver:lt6911uxc_v2.0.6
[    1.350027] lt6911uxc 9-0010: detected lt6911uxc sensor
[    1.526989] tegra-vi4 15700000.vi: subdev lt6911uxc 9-0010 bound

$ v4l2-ctl  --list-devices
vi-output, lt6911uxc 9-0010 (platform:15700000.vi:0):
	/dev/video0

~$v4l2-ctl --all
Driver Info (not using libv4l2):
	Driver name   : tegra-video
	Card type     : vi-output, lt6911uxc 9-0010
	Bus info      : platform:15700000.vi:0
	Driver version: 4.9.201
	Capabilities  : 0x84200001
		Video Capture
		Streaming
		Extended Pix Format
		Device Capabilities
	Device Caps   : 0x04200001
		Video Capture
		Streaming
		Extended Pix Format
Priority: 2
Video input : 0 (Camera 0: no power)
Format Video Capture:
	Width/Height      : 1920/1080
	Pixel Format      : 'AR24'
	Field             : None
	Bytes per Line    : 7680
	Size Image        : 8294400
	Colorspace        : sRGB
	Transfer Function : Default (maps to sRGB)
	YCbCr/HSV Encoding: Default (maps to ITU-R 601)
	Quantization      : Default (maps to Full Range)
	Flags             : 

Camera Controls

                    bypass_mode 0x009a2064 (intmenu): min=0 max=1 default=0 value=0
                override_enable 0x009a2065 (intmenu): min=0 max=1 default=0 value=0
                   height_align 0x009a2066 (int)    : min=1 max=16 step=1 default=1 value=1
                     size_align 0x009a2067 (intmenu): min=0 max=2 default=0 value=0
               write_isp_format 0x009a2068 (int)    : min=1 max=1 step=1 default=1 value=1
       sensor_signal_properties 0x009a2069 (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
        sensor_image_properties 0x009a206a (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
      sensor_control_properties 0x009a206b (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
              sensor_dv_timings 0x009a206c (u32)    : min=0 max=0 step=0 default=0 flags=read-only, has-payload
               low_latency_mode 0x009a206d (bool)   : default=0 value=0
               preferred_stride 0x009a206e (int)    : min=0 max=65535 step=1 default=0 value=0
                   sensor_modes 0x009a2082 (int)    : min=0 max=30 step=1 default=30 value=1 flags=read-only

Could you give me some suggestions? Thanks.

3

hello yunhuzhou,

may I know what’s your pipeline to enable the bridge driver for capturing frames?
could you please also share the kernel messages for reference, thanks

4

Sorry. I don’t understand “may I know what’s your pipeline to enable the bridge driver for capturing frames”. Can you describe it more simply?
Here is the dmesg log file.
dmesg_log.txt (63.8 KB)

5

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

how you enable the camera stream, please share your command-line for reference.