From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Sascha Hauer <sha@pengutronix.de>
Subject: RE: [PATCH 2/4] wifi: rtw88: usb: Update the RX stats after every frame
Date: Tue, 30 Jul 2024 03:59:21 +0000 [thread overview]
Message-ID: <4f24ea4a32e14830b7d47f29870ad263@realtek.com> (raw)
In-Reply-To: <47a89cd7-7767-4b41-abf4-7197e977b7c4@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> Update the number of received unicast data frames and bytes every time
> a frame is received. This is what the PCI and SDIO drivers do.
>
> This has an influence on the power saving, bluetooth coexistence, and
> (in a future patch) the use of RX aggregation.
>
> Tested with RTL8811CU and RTL8723DU.
>
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2024-07-30 3:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 19:39 [PATCH 1/4] wifi: rtw88: Init RX burst length for 8822cu/8822bu/8821cu Bitterblue Smith
2024-07-28 19:41 ` [PATCH 2/4] wifi: rtw88: usb: Update the RX stats after every frame Bitterblue Smith
2024-07-30 3:59 ` Ping-Ke Shih [this message]
2024-07-28 19:42 ` [PATCH 3/4] wifi: rtw88: usb: Support RX aggregation Bitterblue Smith
2024-07-30 4:33 ` Ping-Ke Shih
2024-07-31 16:58 ` Bitterblue Smith
2024-07-30 6:39 ` Sascha Hauer
2024-07-31 16:58 ` Bitterblue Smith
2024-07-28 19:44 ` [PATCH 4/4] wifi: rtw88: Enable USB RX aggregation for 8822c/8822b/8821c Bitterblue Smith
2024-07-30 5:47 ` Ping-Ke Shih
2024-07-31 17:00 ` Bitterblue Smith
2024-08-01 2:08 ` Ping-Ke Shih
2024-07-30 3:57 ` [PATCH 1/4] wifi: rtw88: Init RX burst length for 8822cu/8822bu/8821cu Ping-Ke Shih
2024-07-31 16:57 ` Bitterblue Smith
2024-08-01 2:05 ` 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=4f24ea4a32e14830b7d47f29870ad263@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
--cc=sha@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).