Did the JP5.0 come with a drop of Omnivision OV5693 CSI devkit sensor driver support?

[_av]

the Omnivision OV5693 CSI sensor doesn’t seem listed on JP5.0DP
which was not the case previously with versions up to 4.6.1
Has the driver support been dropped?

/usr/lib/modules/5.10.65-tegra/kernel/drivers/media/i2c$ sudo insmod nv_ov5693.ko

the line above does seem to load the module but doesn’t create /dev/video device

lsmod
Module                  Size  Used by
nv_ov5693              32768  0

[ShaneCCC]

Yes, current J5.0 don’t support E3326 but E3333.
Suppose you can modify the device tree manually to enable it.

[channinglan]

I am using the Jetson AGX Xavier board and camer module ( 699-83326-100-100M + P5V27C )

But can’t see video0 device

tegra194-p2888-0001-p2822-0000.dts (461.7 KB)

DTS is as follows! Is there any error??

[ShaneCCC]

JP5.0 have problem for auto detect the e3326.
Could you please modify the device tree to enable it by using main platform device tree instead of using plugin manager.

https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3261/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/camera_sensor_prog.47.2.html#wwpID0E0XF0HA

[_av]

@ShaneCCC why are not you able to release a simple patch that can be sourced from nvidia addressing that specific narrow issue?
The link[url] shared in the post above seems poorly documented
It appears that it suggests editing .dtsi file at Host PC,
for enabling the video driver to its prior state what edit is required exactly?
What is the proposed simple method[but for reflashing ] to update jetson setup from the file edited at Host PC?
-BR
AV

[ShaneCCC]

We may release device tree overlay(dtbo) for it in future release.