Hi Mikhail,
On 03/28/2014 02:16 PM, Devin Heitmueller wrote:
>>> Let me explain why I created a new thread.
>>> My company is engaged in the monitoring of TV air. All TV channels are
>>> recorded 24/7 for further analysis. But some local TV channels change
>>> the standard over time (SECAM->PAL, PAL->SECAM). So the recording
>>> software must be notified about these changes to set a new standard and
>>> record the picture but not the noise.
>>
>> OK, fair enough.
>
> This is a perfectly reasonable use case, but since we don't do this
> with any other devices we probably need to decide whether this really
> should be the responsibility of the kernel at all, or whether it
> really should be done in userland. Doing it in userland would be
> trivial (even just a script which periodically runs QUERYSTD in a loop
> would accomplish the same thing), and the extra complexity of having a
> thread combined with the inconsistent behavior with all the other
> drivers might make it more worthwhile to do it in userland.
>
> If it were hooked to an interrupt line on the video decoder, I could
> certainly see doing it in kernel, but for something like this the loop
> that checks the standard could just as easily be done in userland.
I agree with Devin here. None of the existing SDTV receivers do this, and
nobody ever used interrupts to check for this. Such interrupts are rarely
available, and if they exists they are never hooked up. This is quite
different for HDTV receivers where such an event is pretty much required
(even though it still isn't officially added to the kernel, but that's
another story).
Is there any reason why your application cannot periodically call QUERYSTD?
The problem you have is not specific to the saa7134, so moving it to the
application is actually a more generic solution since it will work with
any driver that implements querystd.
Adding querystd support to saa7134 in the first place is a good idea
regardless, and I'll test your patch today or Friday.
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
