All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	 Paolo Abeni <pabeni@redhat.com>,  <ath11k@lists.infradead.org>,
	 <linux-wireless@vger.kernel.org>,  <netdev@vger.kernel.org>,
	 <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath11k: Add a warning for wcn6855 spurious wakeup events
Date: Mon, 27 Feb 2023 14:36:46 +0200	[thread overview]
Message-ID: <87r0ubqo81.fsf@kernel.org> (raw)
In-Reply-To: <20230220213807.28523-1-mario.limonciello@amd.com> (Mario Limonciello's message of "Mon, 20 Feb 2023 15:38:07 -0600")

Mario Limonciello <mario.limonciello@amd.com> writes:

> When WCN6855 firmware versions less than 0x110B196E are used with
> an AMD APU and the user puts the system into s2idle spurious wakeup
> events can occur. These are difficult to attribute to the WLAN F/W
> so add a warning to the kernel driver to give users a hint where
> to look.
>
> This was tested on WCN6855 and a Lenovo Z13 with the following
> firmware versions:
> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9
> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23
>
> Link: http://lists.infradead.org/pipermail/ath11k/2023-February/004024.html
> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2377
> Link: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458
> Link: https://lore.kernel.org/linux-gpio/20221012221028.4817-1-mario.limonciello@amd.com/
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>

[...]

> +static void ath11k_check_s2idle_bug(struct ath11k_base *ab)
> +{
> +	struct pci_dev *rdev;
> +
> +	if (pm_suspend_target_state != PM_SUSPEND_TO_IDLE)
> +		return;
> +
> +	if (ab->id.device != WCN6855_DEVICE_ID)
> +		return;
> +
> +	if (ab->qmi.target.fw_version >= WCN6855_S2IDLE_VER)
> +		return;
> +
> +	rdev = pci_get_domain_bus_and_slot(0, 0, PCI_DEVFN(0, 0));
> +	if (rdev->vendor == PCI_VENDOR_ID_AMD)
> +		ath11k_warn(ab, "fw_version 0x%x may cause spurious wakeups. Upgrade to 0x%x or later.",
> +			    ab->qmi.target.fw_version, WCN6855_S2IDLE_VER);

I understand the reasons for this warning but I don't really trust the
check 'ab->qmi.target.fw_version >= WCN6855_S2IDLE_VER'. I don't know
how the firmware team populates the fw_version so I'm worried that if we
ever switch to a different firmware branch (or similar) this warning
might all of sudden start triggering for the users.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	<ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath11k: Add a warning for wcn6855 spurious wakeup events
Date: Mon, 27 Feb 2023 14:36:46 +0200	[thread overview]
Message-ID: <87r0ubqo81.fsf@kernel.org> (raw)
In-Reply-To: <20230220213807.28523-1-mario.limonciello@amd.com> (Mario Limonciello's message of "Mon, 20 Feb 2023 15:38:07 -0600")

Mario Limonciello <mario.limonciello@amd.com> writes:

> When WCN6855 firmware versions less than 0x110B196E are used with
> an AMD APU and the user puts the system into s2idle spurious wakeup
> events can occur. These are difficult to attribute to the WLAN F/W
> so add a warning to the kernel driver to give users a hint where
> to look.
>
> This was tested on WCN6855 and a Lenovo Z13 with the following
> firmware versions:
> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9
> WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23
>
> Link: http://lists.infradead.org/pipermail/ath11k/2023-February/004024.html
> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2377
> Link: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458
> Link: https://lore.kernel.org/linux-gpio/20221012221028.4817-1-mario.limonciello@amd.com/
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>

[...]

> +static void ath11k_check_s2idle_bug(struct ath11k_base *ab)
> +{
> +	struct pci_dev *rdev;
> +
> +	if (pm_suspend_target_state != PM_SUSPEND_TO_IDLE)
> +		return;
> +
> +	if (ab->id.device != WCN6855_DEVICE_ID)
> +		return;
> +
> +	if (ab->qmi.target.fw_version >= WCN6855_S2IDLE_VER)
> +		return;
> +
> +	rdev = pci_get_domain_bus_and_slot(0, 0, PCI_DEVFN(0, 0));
> +	if (rdev->vendor == PCI_VENDOR_ID_AMD)
> +		ath11k_warn(ab, "fw_version 0x%x may cause spurious wakeups. Upgrade to 0x%x or later.",
> +			    ab->qmi.target.fw_version, WCN6855_S2IDLE_VER);

I understand the reasons for this warning but I don't really trust the
check 'ab->qmi.target.fw_version >= WCN6855_S2IDLE_VER'. I don't know
how the firmware team populates the fw_version so I'm worried that if we
ever switch to a different firmware branch (or similar) this warning
might all of sudden start triggering for the users.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2023-02-27 12:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 21:38 [PATCH] wifi: ath11k: Add a warning for wcn6855 spurious wakeup events Mario Limonciello
2023-02-20 21:38 ` Mario Limonciello
2023-02-27 12:36 ` Kalle Valo [this message]
2023-02-27 12:36   ` Kalle Valo
2023-02-27 13:07   ` Mario Limonciello
2023-02-27 13:07     ` Mario Limonciello
2023-02-27 13:14     ` Kalle Valo
2023-02-27 13:14       ` Kalle Valo
2023-02-27 13:19       ` Mario Limonciello
2023-02-27 13:19         ` Mario Limonciello
2023-04-05 10:27         ` Kalle Valo
2023-04-05 10:27           ` Kalle Valo
2023-04-05 20:47           ` Limonciello, Mario
2023-04-05 20:47             ` Limonciello, Mario

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=87r0ubqo81.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.