From: Takashi Iwai <tiwai@suse.de>
To: Gergo Koteles <soyer@irl.hu>
Cc: linux-sound@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: PCI SSID and Codec SSID collision?
Date: Fri, 23 Feb 2024 14:57:43 +0100 [thread overview]
Message-ID: <87sf1j2sh4.wl-tiwai@suse.de> (raw)
In-Reply-To: <d5b42e483566a3815d229270abd668131a0d9f3a.camel@irl.hu>
On Fri, 23 Feb 2024 13:05:12 +0100,
Gergo Koteles wrote:
>
> Hi,
>
> The Lenovo Yoga Slim Pro 9 14IRP8 has tas2781 amplifiers, but it can
> only pickup its fixup with the hda_model=17aa:38be module parameter.
>
> The 17aa:38be is the SSID of its Codec. The PCI SSID is 17aa:3802.
>
> The patch_realtek.c has these fixup:
> SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),
> SND_PCI_QUIRK(0x17aa, 0x38be, "Yoga S980-14.5 proX YC Dual",
> ALC287_FIXUP_TAS2781_I2C),
>
> And the snd_hda_pick_fixup() picks the former fixup because of the same
> PCI SSID, but that is a Codec SSID?
>
> At least it worked without that line.
> https://bugzilla.kernel.org/show_bug.cgi?id=208555#c839
>
> It would be nice if it can be work without the module parameter.
>
> What is the best way to add this strangeness to patch_realtek.c?
That's a bad collision that happens rarely but more than once...
In this case, we'd need to fix 17aa:3802 matching to be a special
function that checks the model more closely. e.g. create a quirk
function that checks the codec SSID additionally and apply the
different quirks from there.
thanks,
Takashi
next prev parent reply other threads:[~2024-02-23 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 12:05 PCI SSID and Codec SSID collision? Gergo Koteles
2024-02-23 13:57 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 14:41 Willian Wang
2024-02-23 14:52 ` Takashi Iwai
2024-02-23 15:10 ` Gergo Koteles
2024-02-23 21:55 ` Willian Wang
2024-02-24 8:35 ` Takashi Iwai
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=87sf1j2sh4.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-sound@vger.kernel.org \
--cc=soyer@irl.hu \
/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