On 08/30/2011 12:14 AM, Pierre-Louis Bossart wrote:
Since modern HDMI cards often have more than one output pin and thus input device, we need to know which one has actually been plugged in. This patch adds a name hint that indicates which PCM device is connected to which pin.
I've been thinking about this, and there's some additional work needed for the jack-detection to be useful. User-space code will need at some point to rely on the ELD information to know what the HDMI receiver supports, eg to enable/disable passthrough.
Meanwhile, at the PulseAudio side, Colin (and Arun?) have made it possible to set capabilities manually in PulseAudio, based on the assumption that the ELD information is often wrong anyway. (?)
I hacked a while ago a small patch to make the ELD bytes available in a control (see attached). It seems to work but I wasn't too sure how to expose it.
I'm assuming that if you have four HDMI pins (or codecs) that will be four "ELD Bytes" controls?
Also, are we sure we want to expose something as driver specific as ELD bytes through that interface, or do we want to do something more generic? (That said, exposing ELD bytes could also be an interim solution while thinking about something more generic.)
Should we define a convention for the name of this control as well?
Note that my patch doesn't change the name of a control but an input device.
Or is there a way to link a control to a specify PCM device?
Unfortunately not - maybe this is something to discuss at Linuxcon Prague?