On 15-12-2011 10:33, javier Martin wrote: > On 15 December 2011 13:01, javier Martin > <javier.martin@xxxxxxxxxxxxxxxxx> wrote: >>> The mx2_camera needs some code to forward calls to S_INPUT/S_ROUTING to >>> tvp5150, in order to set the pipelines there. >> >> This sounds like a sensible solution I will work on that soon. >> > > Hi Mauro, > regarding this subject it seems soc-camera assumes the attached sensor > has only one input: input 0. This means I am not able to forward > S_INPUT/S_ROUTING as you suggested: > http://lxr.linux.no/#linux+v3.1.5/drivers/media/video/soc_camera.c#L213 Then, you need to submit a patch for soc_camera, in order to allow it to work with devices that provide more than one input. > This trick is clearly a loss of functionality because it restricts > sensors to output 0, but it should work since the subsystem can assume > a sensor whose inputs have not been configured has input 0 as the one > selected. > > However, this trick in the tvp5150 which selects input 1 (instead of > 0) as the default input is breaking that assumption. The solution > could be either apply my patch to set input 0 (COMPOSITE0) as default > or swap input numbers so that COMPOSITE1 input is input 0. > > Personally I find my approach more convenient since it matches with > the default behavior expected in the datasheet. Both of your described ways are just hacks. tvp5150 has more than one input. So, the bridge should be supporting the selection between them. Regards, Mauro > > Regards. -- 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
