Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Stefan Binding (Opensource)" <sbinding@opensource.cirrus.com>
Cc: "'Takashi Iwai'" <tiwai@suse.de>,
	"'Heiko Schmid'" <heiko@future-machines.org>,
	<linux-sound@vger.kernel.org>, <tiwai@suse.com>, <perex@perex.cz>
Subject: Re: [PATCH] ALSA: hda: Fix SSID detection for HP Dragonfly Folio G3
Date: Fri, 15 May 2026 13:12:28 +0200	[thread overview]
Message-ID: <8733ztsz8j.wl-tiwai@suse.de> (raw)
In-Reply-To: <000b01dce45b$2dcdef60$8969ce20$@opensource.cirrus.com>

On Fri, 15 May 2026 13:08:37 +0200,
Stefan Binding (Opensource) wrote:
> 
> Hi,
> 
> > -----Original Message-----
> > From: Takashi Iwai <tiwai@suse.de>
> > Sent: Friday, May 15, 2026 10:04 AM
> > To: Heiko Schmid <heiko@future-machines.org>
> > Cc: linux-sound@vger.kernel.org; tiwai@suse.com; perex@perex.cz
> > Subject: Re: [PATCH] ALSA: hda: Fix SSID detection for HP Dragonfly Folio
> G3
> > 
> > On Thu, 14 May 2026 15:31:10 +0200,
> > Heiko Schmid wrote:
> > >
> > > The HP Dragonfly Folio 13.5 inch G3 (PCI SSID 103c:8a05/8a06) BIOS
> > > does not program the PCI subsystem ID correctly when the SOF audio
> > > driver is used. This causes the codec fixup lookup to fail as the PCI
> > > SSID reads as 0x0000:0x0000 instead of the correct 103c:8a06.
> > >
> > > Fix this by falling back to the codec SSID when the PCI SSID is zero,
> > > and add the device-specific quirk entry for the HP Dragonfly Folio G3.
> > >
> > > Signed-off-by: Heiko Schmid <heiko@future-machines.org>
> > 
> > I think the idea is good, but we don't have to restrict to both PCI vendor
> and
> > device being 0; PCI device 0 is used for wildcard, and can't work in
> anyway.
> > 
> > About the patch:
> > 
> > > ---
> > >  sound/hda/codecs/realtek/alc269.c |  2 ++
> > >  sound/hda/common/auto_parser.c    | 10 ++++++++++
> > >  2 files changed, 12 insertions(+)
> > >
> > > diff --git a/sound/hda/codecs/realtek/alc269.c
> > > b/sound/hda/codecs/realtek/alc269.c
> > > index 22b2f67..494dd0a 100644
> > > --- a/sound/hda/codecs/realtek/alc269.c
> > > +++ b/sound/hda/codecs/realtek/alc269.c
> > > @@ -6990,6 +6990,8 @@ static const struct hda_quirk alc269_fixup_tbl[] =
> > {
> > >  	SND_PCI_QUIRK(0x103c, 0x89ae, "HP EliteBook 650 G9",
> > ALC236_FIXUP_HP_GPIO_LED),
> > >  	SND_PCI_QUIRK(0x103c, 0x89c0, "HP ZBook Power 15.6 G9",
> > ALC245_FIXUP_CS35L41_SPI_2_HP_GPIO_LED),
> > >  	SND_PCI_QUIRK(0x103c, 0x8a06, "HP Dragonfly Folio 13.5 G3",
> > > ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED),
> > > +	SND_PCI_QUIRK(0x103c, 0x8a06, "HP Dragonfly Folio 13.5 G3",
> > ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED),
> > > +	SND_PCI_QUIRK(0x103c, 0x8a06, "HP Dragonfly Folio 13.5 G3",
> > > +ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED),
> > 
> > Those additions are simply superfluous, no?  Also...
> 
> We've investigated laptop 103c:8a06 before. Unfortunately, it requires a
> BIOS update for Linux support, since it's a 4 amp laptop, but only has 2 SPI
> resources in ACPI.
> Even if you add the entries, it shouldn't work. I also don't see the
> "original" entry in the repository anywhere - there should be no entry for
> this laptop. 

Thanks for the information.

The quirk matching fix would be still useful, though, so I'm going to
pick it.


Takashi

  reply	other threads:[~2026-05-15 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 13:31 [PATCH] ALSA: hda: Fix SSID detection for HP Dragonfly Folio G3 Heiko Schmid
2026-05-15  9:03 ` Takashi Iwai
     [not found]   ` <04D6DA87-AFD0-44CA-800E-0BA15BEAEA61@getmailspring.com>
2026-05-15 10:48     ` Takashi Iwai
2026-05-15 11:08   ` Stefan Binding (Opensource)
2026-05-15 11:12     ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-29  9:53 Heiko Schmid

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=8733ztsz8j.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=heiko@future-machines.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sbinding@opensource.cirrus.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