From: Ping-Ke Shih <pkshih@realtek.com>
To: Mingcong Bai <jeffbai@aosc.io>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Kexy Biscuit <kexybiscuit@aosc.io>,
Liangliang Zou <rawdiamondmc@outlook.com>,
"John W. Linville" <linville@tuxdriver.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [RFC PATCH] wifi: rtlwifi: disable ASPM for RTL8723BE with subsystem ID 11ad:1723
Date: Tue, 22 Apr 2025 01:21:06 +0000 [thread overview]
Message-ID: <6f0234bc99094b3d84959afd4eea55d7@realtek.com> (raw)
In-Reply-To: <985175be-de04-4d1d-a859-fa740d87c9c3@aosc.io>
Mingcong Bai <jeffbai@aosc.io> wrote:
> Hi Ping-Ke,
>
> 在 2025/4/22 08:27, Ping-Ke Shih 写道:
> > Mingcong Bai <jeffbai@aosc.io> wrote:
> >
>
> <snip>
>
> >>
> >> Please note, however, before the rtl8723be finishes probing, the AER
> >> errors remained. After the module finishes probing, all AER errors would
> >> indeed be eliminated, along with heavy lags, poor network throughput,
> >> and/or occasional lock-ups.
> >
> > Let me clarify here means. Do you mean all work well after applying this
> > patch? Or still lag, poor throughput or lock-ups?
> >
> > If all symptoms disappear, it would be worth to take this (quirk) patch.
>
> Indeed, everything works well after this patch, save for the remaining
> AER errors during driver probing.
Good. Then make a formal patch.
By the way, currently wireless tree runs build testing with NIPA, so please
specify rtw-next tree this patch is going to.
i.e. "[PATCH rtw-next] wifi: rtlwifi: ..."
next prev parent reply other threads:[~2025-04-22 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-19 8:12 [RFC PATCH] wifi: rtlwifi: disable ASPM for RTL8723BE with subsystem ID 11ad:1723 Mingcong Bai
2025-04-22 0:27 ` Ping-Ke Shih
2025-04-22 1:08 ` Mingcong Bai
2025-04-22 1:21 ` Ping-Ke Shih [this message]
2025-04-22 1:37 ` Mingcong Bai
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=6f0234bc99094b3d84959afd4eea55d7@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=jeffbai@aosc.io \
--cc=kexybiscuit@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rawdiamondmc@outlook.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