[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGoCfiyu+iGmy4pu8UQE8YrN=RUBAda4HD0PDjboq8QJTh0dnw@mail.gmail.com>
Date: Mon, 14 Nov 2016 09:16:08 -0500
From: Devin Heitmueller <dheitmueller@...nellabs.com>
To: Hans Verkuil <hverkuil@...all.nl>
Cc: Steve Longerbeam <slongerbeam@...il.com>,
Lars-Peter Clausen <lars@...afoo.de>, mchehab@...nel.org,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Steve Longerbeam <steve_longerbeam@...tor.com>,
Mauro Carvalho Chehab <mchehab@....samsung.com>
Subject: Re: [PATCH v4 7/8] v4l: Add signal lock status to source change events
> 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 delivers blue or
black video with no signal present)? In that case it might still be
useful to inform the application so it can show a message that says
something like "No Signal".
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
Powered by blists - more mailing lists