Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: "Lin, Mengdong" <mengdong.lin@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
	"tiwai@suse.de" <tiwai@suse.de>,
	"Wang, Xingchao" <xingchao.wang@intel.com>,
	"Li, Jocelyn" <jocelyn.li@intel.com>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	James M Leddy <james.leddy@canonical.com>
Subject: Re: [RFC PATCH] ALSA: hda - Ignore default pin config on Haswell HDMI codecs
Date: Tue, 04 Jun 2013 12:19:57 +0200	[thread overview]
Message-ID: <51ADBF4D.30407@canonical.com> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F80123BA2C@SHSMSX101.ccr.corp.intel.com>

On 06/04/2013 12:10 PM, Lin, Mengdong wrote:
> Hi David,
>
> Do you mean that a pin's default configuration may tell "No physical connection" by mistake?

A pin's default configuration can be set to "No physical connection". 
I've seen this on one machine that we're trying to enable.

Whether that is a mistake or not, that's the million dollar question here:

If it is not a mistake, then the graphics driver/stack should pay 
attention to this value, and not route audio to that pin.

If it is a mistake, then the bspec [1] should mention that programming 
of this value should not be allowed (so we can tell the OEM to correct 
their BIOS).

I'm still trying to get a clear answer from someone at Intel, and it's 
becoming a bit frustrating not to get that.


>
> Thanks
> Mengdong
>
>> -----Original Message-----
>> From: David Henningsson [mailto:david.henningsson@canonical.com]
>> Sent: Tuesday, June 04, 2013 4:03 PM
>> To: alsa-devel@alsa-project.org
>> Cc: tiwai@suse.de; Wang, Xingchao; daniel@ffwll.ch; Lin, Mengdong; Girdwood,
>> Liam R; Li, Jocelyn; David Henningsson
>> Subject: [RFC PATCH] ALSA: hda - Ignore default pin config on Haswell HDMI
>> codecs
>>
>> According to Daniel Vetter, these pin configs should be ignored, because the
>> graphics driver/userspace could route audio to these pins even if they are
>> disabled by BIOS.
>>
>> Signed-off-by: David Henningsson <david.henningsson@canonical.com>
>> ---
>>   sound/pci/hda/patch_hdmi.c |   10 ++++++----
>>   1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> It would be good to have this acked by someone at Intel before committing.
>>
>> diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c index
>> e12f7a0..8c1bede 100644
>> --- a/sound/pci/hda/patch_hdmi.c
>> +++ b/sound/pci/hda/patch_hdmi.c
>> @@ -1307,12 +1307,14 @@ static int hdmi_add_pin(struct hda_codec *codec,
>> hda_nid_t pin_nid)
>>   	if (!(caps & (AC_PINCAP_HDMI | AC_PINCAP_DP)))
>>   		return 0;
>>
>> -	config = snd_hda_codec_get_pincfg(codec, pin_nid);
>> -	if (get_defcfg_connect(config) == AC_JACK_PORT_NONE)
>> -		return 0;
>> -
>>   	if (codec->vendor_id == 0x80862807)
>>   		intel_haswell_fixup_connect_list(codec, pin_nid);
>> +	else {
>> +		/* On Haswell, default pin config should be ignored */
>> +		config = snd_hda_codec_get_pincfg(codec, pin_nid);
>> +		if (get_defcfg_connect(config) == AC_JACK_PORT_NONE)
>> +			return 0;
>> +	}
>>
>>   	pin_idx = spec->num_pins;
>>   	per_pin = snd_array_new(&spec->pins);
>> --
>> 1.7.9.5
>



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

[1] Or some other document. I don't have access to the bspec, so I can't 
check this for myself.

  reply	other threads:[~2013-06-04 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  8:02 [RFC PATCH] ALSA: hda - Ignore default pin config on Haswell HDMI codecs David Henningsson
2013-06-04 10:10 ` Lin, Mengdong
2013-06-04 10:19   ` David Henningsson [this message]
2013-06-04 16:23     ` Wang, Xingchao
2013-06-04 15:26 ` Wang, Xingchao

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=51ADBF4D.30407@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel@ffwll.ch \
    --cc=james.leddy@canonical.com \
    --cc=jocelyn.li@intel.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=tiwai@suse.de \
    --cc=xingchao.wang@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