The ov5693 driver needs to be “built-in” in the kernel, i.e. not compiled as a .ko module which gets loaded at a later time during kernel booting process. The real problem is tegra vi/channel driver code does not handle sensor drivers as modules correctly.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| jetson xavier hdmitocsi debug v4l2-compliance ''Unable to handle kernel NULL pointer dereference at virtual address 000001e0" | 17 | 1910 | October 18, 2021 | |
| V4l2 subdev ioctl problem | 23 | 185 | September 5, 2024 | |
| V4l2 subdev problem | 6 | 699 | January 30, 2024 | |
| Gmsl camera can not be registered as V4L2 sub device | 14 | 679 | July 6, 2022 | |
| V4L2 timeout leads to NULL pointer dereference in kernel in jetpack 4.6 | 14 | 4295 | October 18, 2021 | |
| VI hasn't found active link | 5 | 998 | October 18, 2021 | |
| Have a unknow kernel panic when exec the v4l2_async_register_subdev func | 2 | 646 | September 13, 2022 | |
| patched tc358840 driver failing after 28.2 upgrade | 3 | 1027 | October 18, 2021 | |
| Jetpack-5.0.2 migration : tegra camera subdev registration failed | 4 | 1157 | December 7, 2022 | |
| nvcsi on the JetsonTX2 for custom driver | 27 | 3543 | October 18, 2021 |