mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-11-23 02:01:12 +00:00
0b65f667af
Certain V4L2 drivers can report that a video receiver is seeing some signal, but that it is unable to synchronize to it. IOW: the driver can sometimes report V4L2_IN_ST_NO_SYNC and not report V4L2_IN_ST_NO_SIGNAL. In particular, I've seen the tc358743 (HDMI-to-CSI2 converter) driver sometimes report this when deployed to a fleet of embedded Raspberry Pis. The relevant kernel code is in [1]. The video output is not practically usable when V4L2_IN_ST_NO_SYNC is reported (only visually corrupted frames, sometimes with random "snow", are received). I assume that this happens when either the HDMI cable is poorly plugged in or damaged or when a CSI2 FFC cable is used and is damaged. The change in this commit is useful for detecting this working-but-not-really condition in application code. Applications already listening for the "Signal lost" message will gain the ability to handle this condition. There seem to be more V4L2 error flags like this, see [2]. However, I do not have practical experience with them and adding only V4L2_IN_ST_NO_SYNC seems like a safer option. [1]: https://github.com/raspberrypi/linux/blob/be8498ee21aa/drivers/media/i2c/tc358743.c#L1534 [2]: https://www.kernel.org/doc/html/v6.6/userspace-api/media/v4l/vidioc-enuminput.html Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7021> |
||
|---|---|---|
| .. | ||
| directsound | ||
| oss | ||
| oss4 | ||
| osxaudio | ||
| osxvideo | ||
| rpicamsrc | ||
| v4l2 | ||
| waveform | ||
| ximage | ||
| meson.build | ||