From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: jjohnson@kernel.org, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] wifi: ath11k: Add missing platform IDs for quirk table
Date: Tue, 30 Sep 2025 10:17:41 +0800 [thread overview]
Message-ID: <83de6105-ef4c-48dc-8960-430893ae253e@oss.qualcomm.com> (raw)
In-Reply-To: <20250929192146.1789648-1-mpearson-lenovo@squebb.ca>
On 9/30/2025 3:21 AM, Mark Pearson wrote:
> Lenovo platforms can come with one of two different IDs.
> The pm_quirk table was missing the second ID for each platform.
>
> Add missing ID and some extra platform identification comments.
> Reported on https://bugzilla.kernel.org/show_bug.cgi?id=219196
>
> Tested-on: P14s G4 AMD.
Leave a blank line as 'Tested-on:' is not an official tag
> Fixes: ce8669a27016 ("wifi: ath11k: determine PM policy based on machine model")
Better to move the bugzilla link here and reword as below?
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219196
> Signed-off-by: Mark Pearson <mpearson-lenovo@squebb.ca>
> ---
> Changes in v2:
> - Correct typo for T14s G4 AMD to use correct ID. Sorry!
> - Added in Fixes and Tested-on tags correctly.
>
> drivers/net/wireless/ath/ath11k/core.c | 54 +++++++++++++++++++++++---
> 1 file changed, 48 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath11k/core.c b/drivers/net/wireless/ath/ath11k/core.c
> index d49353b6b2e7..47522fa186a1 100644
> --- a/drivers/net/wireless/ath/ath11k/core.c
> +++ b/drivers/net/wireless/ath/ath11k/core.c
> @@ -912,42 +912,84 @@ static const struct ath11k_hw_params ath11k_hw_params[] = {
> static const struct dmi_system_id ath11k_pm_quirk_table[] = {
> {
> .driver_data = (void *)ATH11K_PM_WOW,
> - .matches = {
> + .matches = { /* X13 G4 AMD #1 */
> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "21J3"),
> + },
> + },
> + {
> + .driver_data = (void *)ATH11K_PM_WOW,
> + .matches = { /* X13 G4 AMD #2 */
> DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> DMI_MATCH(DMI_PRODUCT_NAME, "21J4"),
> },
> },
> {
> .driver_data = (void *)ATH11K_PM_WOW,
> - .matches = {
> + .matches = { /* T14 G4 AMD #1 */
> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "21K3"),
> + },
> + },
> + {
> + .driver_data = (void *)ATH11K_PM_WOW,
> + .matches = { /* T14 G4 AMD #2 */
> DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> DMI_MATCH(DMI_PRODUCT_NAME, "21K4"),
> },
> },
> {
> .driver_data = (void *)ATH11K_PM_WOW,
> - .matches = {
> + .matches = { /* P14s G4 AMD #1 */
> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "21K5"),
> + },
> + },
> + {
> + .driver_data = (void *)ATH11K_PM_WOW,
> + .matches = { /* P14s G4 AMD #2 */
> DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> DMI_MATCH(DMI_PRODUCT_NAME, "21K6"),
> },
> },
> {
> .driver_data = (void *)ATH11K_PM_WOW,
> - .matches = {
> + .matches = { /* T16 G2 AMD #1 */
> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "21K7"),
> + },
> + },
> + {
> + .driver_data = (void *)ATH11K_PM_WOW,
> + .matches = { /* T16 G2 AMD #2 */
> DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> DMI_MATCH(DMI_PRODUCT_NAME, "21K8"),
> },
> },
> {
> .driver_data = (void *)ATH11K_PM_WOW,
> - .matches = {
> + .matches = { /*P16s G2 AMD #1 */
> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "21K9"),
> + },
> + },
> + {
> + .driver_data = (void *)ATH11K_PM_WOW,
> + .matches = { /*P16s G2 AMD #2 */
> DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> DMI_MATCH(DMI_PRODUCT_NAME, "21KA"),
> },
> },
> {
> .driver_data = (void *)ATH11K_PM_WOW,
> - .matches = {
> + .matches = { /*T14s G4 AMD #1 */
> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "21F8"),
> + },
> + },
> + {
> + .driver_data = (void *)ATH11K_PM_WOW,
> + .matches = { /*T14s G4 AMD #2 */
> DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
> DMI_MATCH(DMI_PRODUCT_NAME, "21F9"),
> },
assuming Jeff can resolve above nits ...
Reviewed-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
next prev parent reply other threads:[~2025-09-30 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 19:21 Mark Pearson
2025-09-30 2:17 ` Baochen Qiang [this message]
2025-09-30 12:05 ` Mark Pearson
2025-09-30 14:48 ` Jeff Johnson
2025-10-02 0:11 ` Jeff Johnson
2025-10-02 0:37 ` Mark Pearson
2025-10-06 16:51 ` Jeff Johnson
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=83de6105-ef4c-48dc-8960-430893ae253e@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
/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®