I have misinformation on the veyecam driver when kernel init.
I have seen wrong information the the camera driver may be involved when V4l2 * installation but it is on the case when the camera drivers is just modules and not built-in drivers.
When my camera driver is involved as built in , it is not related to v4l2 installation and it should show the driver probing messege or… but my carrier board does not shows anythings.
So it may be from the mistake of menuconfig checking problem or Kconfigs.
the attached photo shows the existance of veyecam driver and deserializer ds90ub954…
Quickly looking over the dmesg the issue might be with your deserializer driver:
[ 1.220375] tegra-i2c 3180000.i2c: no acknowledge from address 0x30
[ 1.220654] i2c-ds90ub954 32-0030: Cannot read register 0x00 (-121)!
[ 1.220657] i2c-ds90ub954 32-0030: ds90ub954_probe: error initializing ds90ub954
[ 1.220791] i2c-ds90ub954: probe of 32-0030 failed with error -121
After this, since the deserializer driver wasn’t initialized correctly neither the camera nor the serializer would be loaded at all.
You might want to look into checking why reading from a register isn’t working. This can be either due to a misconfiguration of the i2c-mux or the deserializer might need a GPIO to be enabled so that it is powered on.