I’m experiencing some weird behaviors testing a custom kernel driver for a camera in a custom board using Jetpack 3.2.1 and TX2. It looks like when starting the board, the tegra-camera platform driver fails to probe, causing the camera to not work at all.
We know our driver works because for a different carrier board it is working without problems. And also, I can capture using v4l2src properly, but nvcamerasrc gets stuck and never starts.
This is the error I’m getting with dmesg:
nvidia@tegra-ubuntu:~$ dmesg | grep -i camera [ 0.582637] tegra_camera_platform tegra-camera-platform: tegra_camera_probe:camera_platform_driver probe [ 0.583175] misc tegra_camera_ctrl: tegra_camera_isomgr_register isp_iso_bw=3925327, vi_iso_bw=1500000, max_bw=3925327 [ 0.583245] __tegra_isomgr_register(): iso bandwidth 3925327KB is not available, client tegra_camera_ctrl [ 0.583291] misc tegra_camera_ctrl: tegra_camera_isomgr_register: unable to register to isomgr [ 0.583326] misc tegra_camera_ctrl: tegra_camera_probe: failed to register CAMERA as isomgr client [ 0.583378] tegra_camera_platform: probe of tegra-camera-platform failed with error -12
Something interesting is that if I disabled all my patches, letting the L4T 28.2 sources as default, the same errors appear. So that I’m not sure if this is a hardware problem or not.
Also, digging a little bit into the source code, it looks like the issue is related to these settings that shows 0 in dmesg:
[ 0.466066] isomgr_init(): iso emc max clk=0KHz [ 0.466084] isomgr_init(): max_iso_bw=0KB
Could you please help me to understand what does this mean?
If the tegra-camera platform driver doesn’t probe, nvcamerasrc won’t work, is that correct?
What difference between the TX1 and TX2 could be causing this problem? I’m asking because with TX1 the problem doesn’t appear.
Thanks for your help on this.