Re: [PATCH v4 7/8] v4l: Add signal lock status to source change events

2016-11-14 Thread Steve Longerbeam
On 11/14/2016 11:19 AM, Steve Longerbeam wrote: On 11/14/2016 03:36 AM, Hans Verkuil wrote: On 08/03/2016 08:03 PM, Steve Longerbeam wrote: Add a signal lock status change to the source changes bitmask. This indicates there was a signal lock or unlock event detected at the input of a video

Re: [PATCH v4 7/8] v4l: Add signal lock status to source change events

2016-11-14 Thread Steve Longerbeam
On 11/14/2016 03:36 AM, Hans Verkuil wrote: On 08/03/2016 08:03 PM, Steve Longerbeam wrote: Add a signal lock status change to the source changes bitmask. This indicates there was a signal lock or unlock event detected at the input of a video decoder. Signed-off-by: Steve Longerbeam

Re: [PATCH v4 7/8] v4l: Add signal lock status to source change events

2016-11-14 Thread Devin Heitmueller
> OK, but what can the application do with that event? If the glitch didn't > affect the video, then it is pointless. > > If the lock is lost, then normally you loose video as well. If not, then > applications are not interested in the event. What about free running mode (where some decoders

Re: [PATCH v4 7/8] v4l: Add signal lock status to source change events

2016-11-14 Thread Hans Verkuil
On 08/03/2016 08:03 PM, Steve Longerbeam wrote: > Add a signal lock status change to the source changes bitmask. > This indicates there was a signal lock or unlock event detected > at the input of a video decoder. > > Signed-off-by: Steve Longerbeam > Cc: Mauro