On 19.12.2013 18:59, Devin Heitmueller wrote:
I haven't
looked situation more carefully yet, but one thing that must be done at the
very first is to add some lock to prevent only DVB or V4L2 API could access
the hardware at time.
Probably worth mentioning that we have *lots* of devices that suffer
from this problem. Our general tact has to been to do nothing and let
the driver crash and burn in non-predictable ways when userland tries
to use both APIs at the same time.
So while it's pretty pathetic that we still haven't resolved this
after all these years, if you didn't address the issue in the initial
release then you wouldn't be much worse off than lots of other
devices.
I think I could add some lock quite easily. I remember when I
implemented cxd2820r DVB-T/T2/C demod driver and at the time it
implements 2 frontends, one for DVB-T/T2 and one for DVB-C. I used
shared lock to prevent access only for single fe at time. I think same
solution works in that case too.
regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
