From: Takashi Iwai <tiwai@suse.de>
To: Willian Wang <kernel@willian.wang>
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org, soyer@irl.hu
Subject: Re: PCI SSID and Codec SSID collision?
Date: Fri, 23 Feb 2024 15:52:17 +0100 [thread overview]
Message-ID: <87le7b2py6.wl-tiwai@suse.de> (raw)
In-Reply-To: <170869932581.7.612391552809015627.273152461@willian.wang>
On Fri, 23 Feb 2024 15:41:26 +0100,
Willian Wang wrote:
>
> Hi, I'm curious about the reasons for the fixup table to be the same
> for PCI and Codec SSIDs and if the PCI SSID is usually more important
> for it to be checked before the Codec.
Sometimes the manufacturers are lazy and didn't check the conflict in
their own products :-<
> Anyway, would a simple
> conditional statement to match these exact PCI and Codec SSID to set
> the fixup manually be enough? There seems to already exist a manual
> fix for TX300 and ROG Strix G17 there (not the same kind of fix and
> with a FIXME comment, though). I have this exact laptop model and
> would like to try to contribute to the code if it's not too
> complicated.
Yes, that's my suggestion. I don't have the data of the other
17aa:3802, but I guess it should have a different codec SSID.
thanks,
Takashi
next prev parent reply other threads:[~2024-02-23 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 14:41 PCI SSID and Codec SSID collision? Willian Wang
2024-02-23 14:52 ` Takashi Iwai [this message]
2024-02-23 15:10 ` Gergo Koteles
2024-02-23 21:55 ` Willian Wang
2024-02-24 8:35 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 12:05 Gergo Koteles
2024-02-23 13:57 ` 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=87le7b2py6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kernel@willian.wang \
--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