From: Ping-Ke Shih <pkshih@realtek.com>
To: Jie Feng <hjf3108@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH rtw-next 2/5] wifi: rtlwifi: rtl8192d: report no signal for frames without PHY status
Date: Mon, 9 Nov 2026 02:51:20 +0000 [thread overview]
Message-ID: <586c158b0fac4a4084f1319ad31f0d5d@realtek.com> (raw)
In-Reply-To: <CABOQOSV0Uys3VigkU4xoT-wfBmRk3UyxJ1KJ5dLDVA6vy=k6tA@mail.gmail.com>
Jie Feng <hjf3108@gmail.com> wrote:
> On Sun, 8 Nov 2026 at 11:13, Ping-Ke Shih <pkshih@realtek.com> wrote:
> >
> > Ho Jie Feng <hjf3108@gmail.com> wrote:
> > > Only the first frame of an A-MPDU comes with the PHY status.
> > > This makes mac80211 report the correct value when queried from iw.
> > >
> > > Test results (2.4 GHz):
> > > before after
> > > TX 6.1 5.2
> > > RX 29.1 27.1
> >
> > How does improper RX_FLAG_NO_SIGNAL_VAL affect throughput?
> I included the throughput numbers as a regression test, to show that it does not
> cause any speed regressions. It should not affect throughput.
Remove the numbers. Or at least mention it doesn't affect throughput.
> > >
> > > Signed-off-by: Ho Jie Feng <hjf3108@gmail.com>
> > > ---
> > > drivers/net/wireless/realtek/rtlwifi/rtl8192d/trx_common.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/drivers/net/wireless/realtek/rtlwifi/rtl8192d/trx_common.c
> > > b/drivers/net/wireless/realtek/rtlwifi/rtl8192d/trx_common.c
> > > index 9f9a34492030c6..a8910cdbfa0979 100644
> > > --- a/drivers/net/wireless/realtek/rtlwifi/rtl8192d/trx_common.c
> > > +++ b/drivers/net/wireless/realtek/rtlwifi/rtl8192d/trx_common.c
> > > @@ -425,6 +425,9 @@ bool rtl92d_rx_query_desc(struct ieee80211_hw *hw, struct rtl_stats *stats,
> > > stats->rx_bufshift);
> > > _rtl92d_translate_rx_signal_stuff(hw, skb, stats, pdesc,
> > > p_drvinfo);
> > > + } else {
> > > + /* Only the first frame of an A-MPDU has the PHY status. */
> >
> > It is clear that this branch is !phystatus, so no need comment.
> Will be removed in v2 of the patch series.
Wait a while, since patchwork and lore for wireless are broken. It is hard
to me to trace patches...
>
> > > + rx_status->flag |= RX_FLAG_NO_SIGNAL_VAL;
> > > }
> > > /*rx_status->qual = stats->signal; */
> > > rx_status->signal = stats->recvsignalpower + 10;
> > > --
> > > 2.53.0
> >
next prev parent reply other threads:[~2026-11-09 2:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261103095256.949327-1-hjf3108@gmail.com>
2026-11-03 9:52 ` [PATCH rtw-next 1/5] wifi: rtlwifi: rc: start no BA session for QoS null frames Ho Jie Feng
2026-11-08 4:08 ` Ping-Ke Shih
2026-11-08 18:11 ` Jie Feng
2026-11-09 2:49 ` Ping-Ke Shih
2026-11-03 9:52 ` [PATCH rtw-next 2/5] wifi: rtlwifi: rtl8192d: report no signal for frames without PHY status Ho Jie Feng
2026-11-08 4:13 ` Ping-Ke Shih
2026-11-08 18:12 ` Jie Feng
2026-11-09 2:51 ` Ping-Ke Shih [this message]
2026-11-03 9:52 ` [PATCH rtw-next 3/5] wifi: rtlwifi: usb: unify the RX code path Ho Jie Feng
2026-11-09 0:40 ` Ping-Ke Shih
2026-11-03 9:52 ` [PATCH rtw-next 4/5] wifi: rtlwifi: rtl8192du: enable USB RX aggregation Ho Jie Feng
2026-11-09 1:44 ` Ping-Ke Shih
2026-11-09 1:53 ` Jie Feng
2026-11-09 2:02 ` Ping-Ke Shih
2026-11-03 9:52 ` [PATCH rtw-next 5/5] wifi: rtlwifi: rtl8192d: let the firmware use all rates Ho Jie Feng
2026-11-09 1:56 ` Ping-Ke Shih
2026-11-09 2:44 ` Jie Feng
2026-11-09 2:58 ` 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=586c158b0fac4a4084f1319ad31f0d5d@realtek.com \
--to=pkshih@realtek.com \
--cc=hjf3108@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.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®