Deskew calibration

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

Hello together,

Is by any chance the requirement of the skew calibration only determined by the pix_clk_hz-property?

Is there a chance that the skew calibration is not required, if I change the VI/CSIVI/ISP clocks from the initial value (lower than 1,5 Gbps) to a higher above the 1,5 Gbps threshold? (That would explain quite a few issues I had in previous image sensor implementations…)

echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee  /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
3

Current the skew calibration did determined by the data output rate(pix_clk_hz/serdes_pix_clk_hz)
Boost the clocks by debugfs won’t trigger it.

Thanks

4

That’s awesome for debugging, thank you!

6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.