From: Ping-Ke Shih <pkshih@realtek.com>
To: Jian-Hong Pan <jhp@endlessos.org>,
Larry Finger <Larry.Finger@lwfinger.net>
Cc: Kalle Valo <kvalo@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@endlessos.org" <linux@endlessos.org>
Subject: RE: [PATCH v2] rtlwifi: rtl8723be: Disable ASPM if RTL8723BE connects to Intel PCI bridge
Date: Tue, 14 Nov 2023 01:41:20 +0000 [thread overview]
Message-ID: <2614f3f7a386435ea7d5f989061c7780@realtek.com> (raw)
In-Reply-To: <20231113043454.10053-2-jhp@endlessos.org>
> -----Original Message-----
> From: Jian-Hong Pan <jhp@endlessos.org>
> Sent: Monday, November 13, 2023 12:35 PM
> To: Larry Finger <Larry.Finger@lwfinger.net>; Ping-Ke Shih <pkshih@realtek.com>
> Cc: Kalle Valo <kvalo@kernel.org>; linux-wireless@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux@endlessos.org; Jian-Hong Pan <jhp@endlessos.org>
> Subject: [PATCH v2] rtlwifi: rtl8723be: Disable ASPM if RTL8723BE connects to Intel PCI bridge
>
> Disable rtl8723be's ASPM if the Realtek RTL8723BE PCIe Wireless adapter
> connects to some Intel PCI bridges, such as Skylake and Kabylake.
> Otherwise, the PCI AER flood hangs system:
>
> pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
> pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
> pcieport 0000:00:1c.5: [ 0] RxErr (First)
> pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
> pcieport 0000:00:1c.5: AER: can't find device of ID00e5
> pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
> pcieport 0000:00:1c.5: AER: can't find device of ID00e5
> pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
> pcieport 0000:00:1c.5: AER: can't find device of ID00e5
>
> Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=218127
Seemingly, you can use "Link" or "Closes" tag.
> Signed-off-by: Jian-Hong Pan <jhp@endlessos.org>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
> ---
> v2: Add the switch case's default condition with comment:
> "The ASPM has already been enabled by initializing
> rtl8723be_mod_params' aspm_support as 1."
>
> .../wireless/realtek/rtlwifi/rtl8723be/sw.c | 24 +++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/drivers/net/wireless/realtek/rtlwifi/rtl8723be/sw.c
> b/drivers/net/wireless/realtek/rtlwifi/rtl8723be/sw.c
> index 43b611d5288d..b20c0b9d8393 100644
> --- a/drivers/net/wireless/realtek/rtlwifi/rtl8723be/sw.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/rtl8723be/sw.c
> @@ -25,10 +25,34 @@ static void rtl8723be_init_aspm_vars(struct ieee80211_hw *hw)
> {
> struct rtl_priv *rtlpriv = rtl_priv(hw);
> struct rtl_pci *rtlpci = rtl_pcidev(rtl_pcipriv(hw));
> + struct pci_dev *bridge_pdev;
>
> /*close ASPM for AMD defaultly */
> rtlpci->const_amdpci_aspm = 0;
>
> + /* Disable ASPM if RTL8723BE connects to some Intel PCI bridges, such as
> + * Skylake and Kabylake. Otherwise, the PCI AER flood hangs system.
> + */
> + bridge_pdev = rtlpci->pdev->bus->self;
> + if (bridge_pdev->vendor == PCI_VENDOR_ID_INTEL) {
> + switch(bridge_pdev->device) {
> + case 0x9d15:
> + /* PCI bridges on Skylake */
> + case 0xa110 ... 0xa11f:
> + case 0xa167 ... 0xa16a:
> + /* PCI bridges on Kabylake */
> + case 0xa290 ... 0xa29f:
> + case 0xa2e7 ... 0xa2ee:
Out of curiosity, do you have so many real platforms to test?
next prev parent reply other threads:[~2023-11-14 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 10:32 [PATCH] rtlwifi: rtl8723be: Disable ASPM if RTL8723BE connects to some Intel PCI bridge Jian-Hong Pan
2023-11-10 20:04 ` Larry Finger
2023-11-13 4:34 ` [PATCH v2] rtlwifi: rtl8723be: Disable ASPM if RTL8723BE connects to " Jian-Hong Pan
2023-11-14 1:41 ` Ping-Ke Shih [this message]
2023-11-14 3:01 ` Jian-Hong Pan
2023-11-14 15:01 ` Jonathan Bither
2023-11-15 10:39 ` Jian-Hong Pan
2023-11-16 4:18 ` [PATCH v3] " Jian-Hong Pan
2023-11-16 16:41 ` Ilpo Järvinen
2023-11-16 17:52 ` Bjorn Helgaas
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=2614f3f7a386435ea7d5f989061c7780@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=jhp@endlessos.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@endlessos.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