alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA: hda: hdmi: Hint matching between input devices and pcm devices
Date: Tue, 30 Aug 2011 09:06:37 +0200	[thread overview]
Message-ID: <4E5C8BFD.3070809@canonical.com> (raw)
In-Reply-To: <1314656063.27660.9.camel@plb-Dell>

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?

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

  reply	other threads:[~2011-08-30  7:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 15:11 ALSA: hda: hdmi: Hint matching between input devices and pcm devices David Henningsson
2011-08-23 15:51 ` Stephen Warren
2011-08-24  4:53   ` David Henningsson
2011-08-24 21:21     ` Stephen Warren
2011-08-25  7:13       ` David Henningsson
2011-08-25 17:41         ` Stephen Warren
2011-08-25 21:37           ` David Henningsson
2011-08-29 22:14             ` Pierre-Louis Bossart
2011-08-30  7:06               ` David Henningsson [this message]
2011-08-30  7:40               ` Clemens Ladisch
2011-08-30 13:01                 ` Pierre-Louis Bossart
     [not found]                 ` <000601cc6714$fc5caa80$f515ff80$@bossart@linux.intel.com>
2011-09-12  7:10                   ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E5C8BFD.3070809@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).