Jamie Lokier wrote at Thursday, January 12, 2012 5:24 AM: ... > For all the above reasons I think the DDC/EDID support in the kernel > should be moving gently towards a (very small) DDC/EDID mini-subsystem > shared by video drivers. I.e. it should be exposed as a well-known > I2C bus name, and if it's GPIO bit-banging I2C, that should be exposed > as well.
I don't think a single well-known bus name would work, since it's very common for a system to have multiple DDC busses, since they have multiple video connectors. However, representing each physical connector as a jack object to user- space (perhaps related to media controller, or a cross-subsystem extension of the ALSA jack objects?) and associating the I2C bus ID (or some more abstract display-oriented ID) with it would make sense. -- nvpublic _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
