mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Paolo Lazzaroni <eexto@aol.com>,
	Ping-Ke Shih <pkshih@realtek.com>, Kalle Valo <kvalo@kernel.org>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Oleksandr Havrylov" <goainwo@gmail.com>,
	"Gabriel Maia" <gabrielvinicius.damaia@gmail.com>,
	"Rahul Kumar Rai" <learn.rahul.rai@gmail.com>,
	"Mihail Dimoski" <mihaildimoski@gmail.com>,
	"Ata İlhan Köktürk" <atailhan2006@gmail.com>
Subject: Re: [PATCH rtw-next] wifi: rtw88: 8821c: disable deep LPS on PCIe devices
Date: Sat, 19 Sep 2026 20:39:01 +0300	[thread overview]
Message-ID: <2f2f2366-bf64-45d1-911d-6a769be9d7aa@gmail.com> (raw)
In-Reply-To: <20260918232801.119348-1-eexto@aol.com>

On 19/09/2026 02:28, Paolo Lazzaroni wrote:
> On RTL8821CE PCIe adapters, entering 32kHz low-power clock deep sleep
> (LPS_DEEP_MODE_LCLK) causes recurrent PCIe completion timeouts,
> "firmware failed to leave lps state", "failed to send h2c command",
> and hard system freezes when transitioning out of low power states with
> PCIe ASPM enabled.
> 
> To work around this, a DMI quirk list (rtw_pci_quirks[]) was introduced
> and has grown across HP, ASUS, Dell, and Lenovo machines. However, DMI
> matching is unsustainable: minor sub-model variances (such as ASUS
> FA506II vs FA506IH) or unlisted models (such as ASUS VivoBook X515JA,
> Bmax Y14, or modern Alder Lake-N mini PCs) leave users experiencing bus
> lockups or firmware drops unless they manually turn off power saving via
> iw.
> 
> Examination of official OEM Windows driver INF files for RTL8821CE
> (HP and ASUS netrtwlane.inf) reveals that vendor drivers explicitly
> disable deep power saving (WoWLANPSMode = 0, bLPS_PG_En = 0) and enable

Disabling LPS_PG doesn't mean disabling LCLK, I think.

> firmware PCIe recovery, while keeping standard PCIe ASPM enabled.
> Furthermore, other chips in rtw88 (RTL8723DE, RTL8812AE, RTL8821AE)
> already set lps_deep_mode_supported = 0 by default.

What those other chips are doing is not relevant. RTL8812AE and
RTL8821AE are not officially supported in rtw88. (Not yet?)
lps_deep_mode_supported is zero in rtw8812a.c and rtw8821a.c because
rtw88_usb doesn't implement deep PS and I didn't research which
modes they could support if deep PS was implemented for USB.

> 
> Conservatively disable LPS_DEEP_MODE_LCLK specifically for RTL8821C on
> PCIe interfaces in rtw_update_lps_deep_mode(). Standard 802.11 LPS
> power saving and PCIe ASPM remain functional, preventing system lockups
> and firmware failures without affecting SDIO or USB variants.
> 
> Signed-off-by: Paolo Lazzaroni <eexto@aol.com>
> ---
>  drivers/net/wireless/realtek/rtw88/main.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/net/wireless/realtek/rtw88/main.c b/drivers/net/wireless/realtek/rtw88/main.c
> index 0f23498b5..5bd854223 100644
> --- a/drivers/net/wireless/realtek/rtw88/main.c
> +++ b/drivers/net/wireless/realtek/rtw88/main.c
> @@ -1360,6 +1360,14 @@ static enum rtw_lps_deep_mode rtw_update_lps_deep_mode(struct rtw_dev *rtwdev,
>  	    !fw->feature)
>  		return LPS_DEEP_MODE_NONE;
>  
> +	/* RTL8821CE PCIe devices fail to wake up from 32kHz LCLK deep sleep
> +	 * in time for PCIe completion deadlines, leading to PCIe bus freeze

Completion timeout is already disabled for this chip.

> +	 * and communication timeouts.
> +	 */
> +	if (rtw_hci_type(rtwdev) == RTW_HCI_TYPE_PCIE &&
> +	    chip->id == RTW_CHIP_TYPE_8821C)
> +		return LPS_DEEP_MODE_NONE;
> +
>  	if ((chip->lps_deep_mode_supported & BIT(LPS_DEEP_MODE_PG)) &&
>  	    rtw_fw_feature_check(fw, FW_FEATURE_PG))
>  		return LPS_DEEP_MODE_PG;

However, I'm not saying it's necessarily wrong to disable deep PS for
this chip completely. I'm just objecting to your LLM's conclusions.

  reply	other threads:[~2026-09-19 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260918232801.119348-1-eexto.ref@aol.com>
2026-09-18 23:28 ` Paolo Lazzaroni
2026-09-19 17:39   ` Bitterblue Smith [this message]
2026-09-20  2:36     ` Ping-Ke Shih

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=2f2f2366-bf64-45d1-911d-6a769be9d7aa@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=atailhan2006@gmail.com \
    --cc=eexto@aol.com \
    --cc=gabrielvinicius.damaia@gmail.com \
    --cc=goainwo@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=learn.rahul.rai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mihaildimoski@gmail.com \
    --cc=pkshih@realtek.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 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®