>> How about this implementation? I know it's not for soc, but I post it >> to give my idea. >> Bridge knows the layout, so it doesn't need to query the subdevice. > > Where from? AFAIU, we are talking here about subdevice inputs, right? In > this case about various inputs of the TV decoder. How shall the bridge > driver know about that? I have asked this question before. Laurent reply me: > >> ENUMINPUT as defined by V4L2 enumerates input connectors available on > >> the board. Which inputs the board designer hooked up is something that > >> only the top-level V4L driver will know. Subdevices do not have that > >> information, so enuminputs is not applicable there. > >> > >> Of course, subdevices do have input pins and output pins, but these are > >> assumed to be fixed. With the s_routing ops the top level driver selects > >> which input and output pins are active. Enumeration of those inputs and > >> outputs wouldn't gain you anything as far as I can tell since the > >> subdevice simply does not know which inputs/outputs are actually hooked > >> up. It's the top level driver that has that information (usually passed > >> in through board/card info structures). Regards, Scott -- 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
