Em Mon, 21 Mar 2016 16:20:09 -0300 Javier Martinez Canillas <javier@xxxxxxxxxxxxxxx> escreveu: > > BTW, if the tvp5150 needs to know which composite connector is connected > > to which hardware pin, then you still may need to be explicit w.r.t. the > > number of pads. I just thought of that. > > > > The tvp5150 doesn't care about that, as Mauro said is just a mux so you can > have logic in the .link_setup that does the mux depending on the remote > entity (that's in fact how I implemented and is currently in mainline). > > Now, the user needs to know which entity is mapped to which input pin. > All its know from the HW documentation is that for example the left > RCA connector is AIP1A and the one inf the right is connected to AIP1B. > > So there could be a convention that the composite connected to AIP1A pin > (the default) is Composite0 and the connected to AIP1B is Composite1. We should avoid a convention here... instead, we should support properties via the properties API to export enough info for userspace to know what physical connectors correspond to each "connection" entity. As we've discussed previously, such properties can be: - connector's name - color - position etc... Regards, Mauro -- 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
