From: Ping-Ke Shih <pkshih@realtek.com>
To: Paolo Lazzaroni <eexto@aol.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: 8821c: Add HP single-antenna quirk
Date: Sun, 20 Sep 2026 01:22:16 +0000 [thread overview]
Message-ID: <4486aa8a910246deb2eef5ff392f9f37@realtek.com> (raw)
In-Reply-To: <20260918195927.30118-1-eexto@aol.com>
Paolo Lazzaroni <eexto@aol.com> wrote:
> > If this is the only one platform which needs this kind of quirk. Add an entry
> > to rtw_pci_quirks[].
>
> Regarding rtw_pci_quirks[]:
>
> The reason I matched the PCI subsystem ID (10ec:c821 [103c:831a]) rather
> than DMI in rtw_pci_quirks[] is that HP assigns this specific subsystem
> ID across a family of laptop platforms (e.g. HP 15-da, 15-db, and related
> chassis) to denote the single physical antenna connected to Aux/S1.
> This is documented in the OEM Windows driver INF (netrtwlane.inf):
> "PCI\VEN_10EC&DEV_C821&SUBSYS_831A103C ;;single ant(connect to right one S1)"
>
> If we use DMI matching in rtw_pci_quirks[], it would only match this specific
> laptop SKU ("HP Laptop 15-da0xxx" / "4XW76EA#ABZ"), leaving other HP models
> sharing this identical 103c:831a single-antenna card with severe signal loss.
>
> However, I understand that inspecting PCI structures inside rtw8821c_read_efuse()
> violates bus abstraction for rtw8821c.c.
>
> Would you prefer:
> Option A: Keep the PCI subsystem match, but handle it cleanly in rtw_pci_probe()
> (e.g., setting a flag or rfe_option override in rtwdev before chip setup)?
> Option B: Add a DMI entry to rtw_pci_quirks[] matching this platform?
I prefer option A, but yes, please handle it cleanly in pci.c.
You can flag a quirk at pci.c, and update rfe_option in 8821c.c.
Ping-Ke
next prev parent reply other threads:[~2026-09-20 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260911100904.50320-1-eexto.ref@aol.com>
2026-09-11 10:09 ` [PATCH] wifi: rtw88: 8821c: Add HP single-antenna quirk not-eexto
2026-09-13 2:15 ` Ping-Ke Shih
2026-09-18 19:59 ` Paolo Lazzaroni
2026-09-20 1:22 ` Ping-Ke Shih [this message]
2026-09-11 10:56 not-eexto
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=4486aa8a910246deb2eef5ff392f9f37@realtek.com \
--to=pkshih@realtek.com \
--cc=eexto@aol.com \
--cc=linux-wireless@vger.kernel.org \
/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