Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] ALSA: hda/hdmi: add force-connect quirk for ASUSTeK Z170M Pro
Date: Mon, 11 Dec 2023 18:52:25 +0200	[thread overview]
Message-ID: <87bkawy94m.fsf@intel.com> (raw)
In-Reply-To: <20231207170723.2371881-1-kai.vehmanen@linux.intel.com>

On Thu, 07 Dec 2023, Kai Vehmanen <kai.vehmanen@linux.intel.com> wrote:
> On ASUSTeK Z170M PRO GAMING + Intel Kaby Lake system the display codec
> pins are not registered properly without the force-connect quirk. The
> codec will report only one pin as having external connectivity, but i915
> finds all all three connectors on the system, so the two drivers are not
> in sync.
>
> Link: https://gitlab.freedesktop.org/drm/intel/-/issues/9801
> Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>

Pushed to topic/core-for-CI.

> ---
>  sound/pci/hda/patch_hdmi.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
> index 3d7f8f510ec7..8bf91fe25c65 100644
> --- a/sound/pci/hda/patch_hdmi.c
> +++ b/sound/pci/hda/patch_hdmi.c
> @@ -1995,6 +1995,7 @@ static const struct snd_pci_quirk force_connect_list[] = {
>  	SND_PCI_QUIRK(0x103c, 0x8715, "HP", 1),
>  	SND_PCI_QUIRK(0x1043, 0x8694, "ASUS", 1),  /* SKL/KBL + PRIME B560M-A */
>  	SND_PCI_QUIRK(0x1043, 0x86ae, "ASUS", 1),  /* SKL + Z170 PRO */
> +	SND_PCI_QUIRK(0x1043, 0x86c7, "ASUS", 1),  /* KBL + Z170M PRO */
>  	SND_PCI_QUIRK(0x1462, 0xec94, "MS-7C94", 1),
>  	SND_PCI_QUIRK(0x8086, 0x2060, "Intel NUC5CPYB", 1),
>  	SND_PCI_QUIRK(0x8086, 0x2081, "Intel NUC 10", 1),

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2023-12-11 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 17:07 [PATCH] ALSA: hda/hdmi: add force-connect quirk for ASUSTeK Z170M Pro Kai Vehmanen
2023-12-08  0:06 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-12-08  0:20 ` ✓ Fi.CI.BAT: success " Patchwork
2023-12-08  7:27   ` Saarinen, Jani
2023-12-08  7:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2023-12-08  8:02   ` Saarinen, Jani
2023-12-08 11:07     ` Kai Vehmanen
2023-12-11 16:52 ` Jani Nikula [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=87bkawy94m.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kai.vehmanen@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