What in the kernel settings causes the imx219 module to be loaded on bootup. Is it a configuration file somewhere? or is it a setting when the kernel is compiled?
I am running an orin nano devkit on 36.3.
What in the kernel settings causes the imx219 module to be loaded on bootup. Is it a configuration file somewhere? or is it a setting when the kernel is compiled?
I am running an orin nano devkit on 36.3.
It is configuration file in tegra_defconfig. You need to check of you have entry for it inside that file.
Refer this below link with similar solution:
This is what I had originally suspected, but when I check that file , there is no CONFIG_VIDEO_IMX219=y
. Yet that imx219 is still loaded at boot time, as shown by dmesg.
I have not modified the source code in anyway either before building and flashing.
My thoughts:
Might be that driver is built as part of kernel image itself
, which is like an in tree module…
The probe function being called at boot up is part of the nvidia-oot module, as it references a board_setup function which is only part of the nv_imx219.c
file in the out of tree module. There is an imx219.c
file in tree however this is just for V4L2 and not the one being called on bootup.
For anyone else that needs to know or runs into a similar issue. You can use the jetson-io.py
file to set the /boot/extlinux/extlinux.conf
or set the extlinux.conf
file manually. This will apply the device tree overlay. However my device tree still wasn’t linking to my device driver like I wanted it to. This is because you need to change the /usr/lib/modules/*-tegra/modules.alias
file for them to “find” each other. Once I modified this I could see my probe function for my device driver was being called like I wanted.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.