From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: tiwai@suse.com
Cc: 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>,
Harsha Priya <harshapriya.n@intel.com>,
"moderated list:SOUND" <alsa-devel@alsa-project.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: hda/hdmi: Use force connectivity quirk on another HP desktop
Date: Wed, 12 Aug 2020 23:43:27 +0800 [thread overview]
Message-ID: <44573652-9ECF-4EC5-A234-DBB21FC90CC7@canonical.com> (raw)
In-Reply-To: <20200811095336.32396-1-kai.heng.feng@canonical.com>
Hi,
> On Aug 11, 2020, at 17:53, Kai-Heng Feng <kai.heng.feng@canonical.com> wrote:
>
> There's another HP desktop has buggy BIOS which flags the Port
> Connectivity bit as no connection.
>
> Apply force connectivity quirk to enable DP/HDMI audio.
>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
I guess this patch was omitted as well...
Kai-Heng
> ---
> 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 4bbd12d3b1b5..b8c8490e568b 100644
> --- a/sound/pci/hda/patch_hdmi.c
> +++ b/sound/pci/hda/patch_hdmi.c
> @@ -1863,6 +1863,7 @@ static int hdmi_add_cvt(struct hda_codec *codec, hda_nid_t cvt_nid)
> }
>
> static const struct snd_pci_quirk force_connect_list[] = {
> + SND_PCI_QUIRK(0x103c, 0x870f, "HP", 1),
> SND_PCI_QUIRK(0x103c, 0x871a, "HP", 1),
> {}
> };
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-08-12 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 9:53 Kai-Heng Feng
2020-08-12 15:43 ` Kai-Heng Feng [this message]
2020-08-12 15:47 ` Takashi Iwai
2020-08-12 16:39 ` Kai-Heng Feng
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=44573652-9ECF-4EC5-A234-DBB21FC90CC7@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=aplattner@nvidia.com \
--cc=harshapriya.n@intel.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®