mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: tiwai@suse.com, Jaroslav Kysela <perex@perex.cz>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Nikhil Mahale <nmahale@nvidia.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Aaron Plattner <aplattner@nvidia.com>,
	"moderated list:SOUND" <alsa-devel@alsa-project.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: hda/hdmi: Add pins with jack detection support
Date: Tue, 04 Aug 2020 13:48:00 +0200	[thread overview]
Message-ID: <s5htuxizl73.wl-tiwai@suse.de> (raw)
In-Reply-To: <21676100-4D83-44F6-BB39-4FDFBDEAF462@canonical.com>

On Tue, 04 Aug 2020 13:42:03 +0200,
Kai-Heng Feng wrote:
> 
> 
> 
> > On Aug 4, 2020, at 17:48, Takashi Iwai <tiwai@suse.de> wrote:
> > 
> > On Tue, 04 Aug 2020 11:31:59 +0200,
> > Kai-Heng Feng wrote:
> >> 
> >> 
> >> 
> >>> On Aug 4, 2020, at 17:04, Takashi Iwai <tiwai@suse.de> wrote:
> >>> 
> >>> On Tue, 04 Aug 2020 09:29:25 +0200,
> >>> Kai-Heng Feng wrote:
> >>>> 
> >>>> HDMI on some platforms doesn't enable audio support because its Port
> >>>> Connectivity [31:30] is set to AC_JACK_PORT_NONE:
> >>>> Node 0x05 [Pin Complex] wcaps 0x40778d: 8-Channels Digital Amp-Out CP
> >>>> Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> >>>> Amp-Out vals:  [0x00 0x00]
> >>>> Pincap 0x0b000094: OUT Detect HBR HDMI DP
> >>>> Pin Default 0x58560010: [N/A] Digital Out at Int HDMI
> >>>>   Conn = Digital, Color = Unknown
> >>>>   DefAssociation = 0x1, Sequence = 0x0
> >>>> Pin-ctls: 0x40: OUT
> >>>> Unsolicited: tag=00, enabled=0
> >>>> Power states:  D0 D3 EPSS
> >>>> Power: setting=D0, actual=D0
> >>>> Devices: 0
> >>>> Connection: 3
> >>>>    0x02 0x03* 0x04
> >>>> 
> >>>> Those pins were filtered out by commit 116dcde63806 ("ALSA: HDA: Remove
> >>>> unconnected PCM devices for Intel HDMI"). However, jacks that support
> >>>> detection won't have the issues the commit addresses.
> >>>> 
> >>>> So still add the pin if it supports jack detection.
> >>>> 
> >>>> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> >>> 
> >>> Which platform did show the problem?
> >> 
> >> An HP desktop.
> > 
> > Well, what I meant was about which codec.  And now I see it in the
> > below.
> > 
> >>> I'm reluctant to apply this change as it would potentially break the
> >>> existing system.  If we must to apply, maybe it's safer to apply it
> >>> conditionally to the limited devices.
> >> 
> >> Hmm, I find it's a bit hard to match a specific device, because the ID seems to be rather generic:
> >> Codec: Intel Kabylake HDMI
> >> Address: 2                      
> >> AFG Function Id: 0x1 (unsol 0)
> >> Vendor Id: 0x8086280b         
> >> Subsystem Id: 0x80860101
> >> Revision Id: 0x100000
> >> 
> >> Should we use DMI string instead?
> > 
> > So it's a Kabylake, and I presume that it's rather an old machine.
> > Is this for docking station or anything else?
> 
> The system is Comet Lake CPU so it's fairly recent. I think most Comet Lake platforms still use "Kabylake HDMI".

OK.

> > Basically the pin capability is rather fixed by the chip design while
> > the pin configuration is set by BIOS.  And we follow the BIOS setup
> > for determining which pins are actually alive.  That said, the bug is
> > a BIOS bug.
> 
> Yes but sometimes vendors are reluctant to fix it because "Windows doesn't have this issue".

Yes, and BIOS is always buggy, it's a fundamental rule of the world :)
So I'm not against adding the workaround itself.  The problem is that
applying the workaround globally would cause another regression.

> > Note that PCI SSID bound with this codec might have a different
> > number, so we might be still able to use the standard quirk table to
> > pick up.
> 
> Ok. Will send v2 with a quirk list.

Thanks.  We can reconsider to widen the application of the workaround
once when we see the requirement (i.e. more machines with buggy BIOS
setup.)


Takashi


> Kai-Heng
> 
> > 
> > 
> > thanks,
> > 
> > Takashi
> > 
> >>> 
> >>> thanks,
> >>> 
> >>> Takashi
> >>> 
> >>>> ---
> >>>> sound/pci/hda/patch_hdmi.c | 3 ++-
> >>>> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>>> 
> >>>> diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
> >>>> index cd46247988e4..db3a5148bd40 100644
> >>>> --- a/sound/pci/hda/patch_hdmi.c
> >>>> +++ b/sound/pci/hda/patch_hdmi.c
> >>>> @@ -1701,7 +1701,8 @@ static int hdmi_add_pin(struct hda_codec *codec, hda_nid_t pin_nid)
> >>>> 	 * all device entries on the same pin
> >>>> 	 */
> >>>> 	config = snd_hda_codec_get_pincfg(codec, pin_nid);
> >>>> -	if (get_defcfg_connect(config) == AC_JACK_PORT_NONE)
> >>>> +	if ((get_defcfg_connect(config) == AC_JACK_PORT_NONE) &&
> >>>> +	    !(caps & AC_PINCAP_PRES_DETECT))
> >>>> 		return 0;
> >>>> 
> >>>> 	/*
> >>>> -- 
> >>>> 2.17.1
> 

      reply	other threads:[~2020-08-04 11:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  7:29 Kai-Heng Feng
2020-08-04  9:04 ` Takashi Iwai
2020-08-04  9:31   ` Kai-Heng Feng
2020-08-04  9:48     ` Takashi Iwai
2020-08-04 11:42       ` Kai-Heng Feng
2020-08-04 11:48         ` Takashi Iwai [this message]

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=s5htuxizl73.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=aplattner@nvidia.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nmahale@nvidia.com \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®