On Tue, 22 Feb 2011, Aguirre, Sergio wrote: > For example, at least OMAP3 & 4 has the following pin pairs: > > CSI2_DX0, CSI2_DY0 > CSI2_DX1, CSI2_DY1 > CSI2_DX2, CSI2_DY2 > CSI2_DX3, CSI2_DY3 > CSI2_DX4, CSI2_DY4 > > So, what you do is that, you can control where do you want the clock, > where do you want each datalane pair, and also the pin polarity > (X: +, Y: -, or viceversa). And this is something that is static. > THIS I think should go in the host driver's platform data. I think, these are two different things: pin roles - yes, they are SoC-specific and, probably, hard-wired. But once you've assigned roles, you have to configure them - roles, functions, not pins. And that configuration is no longer SoC specific, at least some of the parameters are common to all such set ups - polarities and edges. So, you can use the same set of parameters for them on different platforms. And yes - you have to be able to configure them dynamically. Consider two sensors switching to the same host by means of some board logic. So, at least there have to be multiple parameter sets to use, depending on the connection topology. Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/ -- 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
