Hi all,
We have developed a lot of camera drivers for the Jetson platforms, we have noticed something interesting related to the pixel_clk_hz DTB property calculation, If we calculate the value as width x height x framerate (taking in consideration blanking as you have on the camera programming guide Sensor Pixel Clock section) we have not been able to get the drivers working and we get some issues related to the MIPI.
In order to get the drivers working we need to increase that pixel_clk_hz value x10, Do you know why we need to use a bigger value than the calculated?
-Adrian