On Mon May 28 2012 19:25:41 Ezequiel Garcia wrote: > On Mon, May 28, 2012 at 2:10 PM, Hans Verkuil <hverkuil@xxxxxxxxx> wrote: > >> > >> I may be missing something, but I don't see any relation between > >> video buffer queue and selected input. > >> (Perhaps this is OT and we should discuss this in another thread) > > > > Well, this particular API was intended to let the hardware switch from one input > > to another automatically: e.g. the first frame is from input 1, the second from > > input 2, etc. until it has gone through all inputs and goes back to input 1. > > > > This requires hardware support and if the stk1160 can't do that, then you can > > forget about all this. > > I did some tests earlier this morning and apparently the input > switching is done > through some stk1160 GPIO port setting. > However, I'll have to figure this out reading easycap staging driver > and trying different values over and over. > Plus, saa7115 driver supports "s_routing" function, but couldn't make > it work: it looked like saa7115 input > setting was fixed and stk1160 handles the input switching. > > Also, I'm not sure if saa7115 "s_stream" to enable/disable capture is > also working. > Sounds a bit weird to me. > > One last query: I found *no* way to distinguish between one device > (one composite input) > and the other (four composite input). What do you suggest? Just > implement all of them always? If you can't tell them apart, then that would be your only option. You might also add a 'model' module option so users can tell the driver which model it is. Another might be (I don't know if that will work) to try all inputs and see if you can detect a difference in the saa7115: however, I suspect you can't tell the difference between 'I have only one input' and 'I have four but I haven't hooked up anything to my inputs'. I *hate* it when they don't bother to change the USB IDs. > Looks like I'm on the right path anyway :) Yup! Regards, Hans -- 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
