I figured out that it was a loop in vi4_fops.c. It never got the interlaced_type from the device tree, so it was stuck in the capture thread in the top_bottom section. There is a for loop that decrements the counting variable inside the loop, meaning the thread never gets to the point where it checks if it should stop. I just made sure that it always takes the “interleaved” path instead, and that fixed that problem
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Improper frames in PAL | 48 | 2670 | November 10, 2021 | |
| Tegra channel error recovering on Xavier when capturing with v4l2 | 8 | 3209 | October 18, 2021 | |
| Vi-output, tc35 100% loading and No Video Stream with tc358840 4K HDMI to MIPI | 25 | 2343 | February 2, 2022 | |
| HDMI2CSI - Interlaced video for Jetson TX2 | 6 | 1582 | August 13, 2019 | |
| Camera of 960x480i do not work | 60 | 3474 | August 29, 2021 | |
| How to resume VI capture | 14 | 178 | October 9, 2024 | |
| CSI recovery after camera power off/on | 24 | 148 | April 21, 2025 | |
| Capture interlace video on Jetson TX2 | 8 | 1576 | October 18, 2021 | |
| TC358743 Interlaced capture? | 5 | 1014 | October 15, 2021 | |
| Jetpack 5.0.2 : NULL VI channel received & VIFALC_TDSTATE | 2 | 839 | January 25, 2023 |