Hi Michael, On Friday 11 February 2011 13:07:33 Michael Jones wrote: > On 01/27/2011 12:46 AM, Guennadi Liakhovetski wrote: > > Looking at the "Data-Lane Shifter" table (12.27 in my datasheet, in the > > "Bridge-Lane Shifter" chapter), I think, the first two columns are fixed > > by the board design, right? So, our freedom lies only in one line there > > and is a single parameter - the shift value. The output shifter (VPIN) is > > independent from this one, but not unrelated. It seems logical to me to > > relate the former one to CCDC's input pad, and the latter one to CCDC's > > output pad. AFAIU, Laurent, your implementation in what concerns pad > > configuration is: let the user configure all interfaces independently, > > and first when we have to actually activate the pipeline (start > > streaming or configure video buffers) we can verify, whether all parts > > fit together. > > I would like to add this lane shifter support. Would you like me to > implement it as Guennadi suggested- letting the user set all 3 CCDC pad > formats arbitrarily and postpone the consistency checks to streamon time? I've discussed this with Sakari Ailus, and we would implement it with different formats on the sensor output and the CCDC input. I'd like to get Hans Verkuil's opinion. -- Regards, Laurent Pinchart -- 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
