linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>
Subject: RE: [PATCH v3 2/3] wifi: rtl8xxxu: Fix the channel width reporting
Date: Wed, 30 Nov 2022 00:38:34 +0000	[thread overview]
Message-ID: <4959ded326514badbb7bbfbf60e353d4@realtek.com> (raw)
In-Reply-To: <aa0afff7-eccd-eac6-9b0d-6d5e94fb2c06@gmail.com>



> -----Original Message-----
> From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> Sent: Wednesday, November 30, 2022 3:06 AM
> To: linux-wireless@vger.kernel.org
> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>; Ping-Ke Shih <pkshih@realtek.com>
> Subject: [PATCH v3 2/3] wifi: rtl8xxxu: Fix the channel width reporting
> 
> The gen 2 chips RTL8192EU and RTL8188FU periodically send the driver
> reports about the TX rate, and the driver passes these reports to
> sta_statistics. The reports from RTL8192EU may or may not include the
> channel width. The reports from RTL8188FU do not include it.
> 
> Only access the c2h->ra_report.bw field if the report (skb) is big
> enough.
> 
> The other problem fixed here is that the code was actually never
> changing the channel width initially reported by
> rtl8xxxu_bss_info_changed because the value of RATE_INFO_BW_20 is 0.
> 
> Fixes: 0985d3a410ac ("rtl8xxxu: Feed current txrate information for mac80211")
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> ---
> v3:
>  - Don't assume bw will always be 1 byte.
> 
> v2:
>  - Eliminate the magic numbers.
> ---
>  drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c | 11 ++++++++---
>  1 file changed, 8 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> index 28f136064297..9799bc5ed60a 100644
> --- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> +++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu_core.c
> @@ -5569,7 +5569,6 @@ static void rtl8xxxu_c2hcmd_callback(struct work_struct *work)
>  			rarpt->txrate.flags = 0;
>  			rate = c2h->ra_report.rate;
>  			sgi = c2h->ra_report.sgi;
> -			bw = c2h->ra_report.bw;
> 
>  			if (rate < DESC_RATE_MCS0) {
>  				rarpt->txrate.legacy =
> @@ -5586,8 +5585,14 @@ static void rtl8xxxu_c2hcmd_callback(struct work_struct *work)
>  						RATE_INFO_FLAGS_SHORT_GI;
>  				}
> 
> -				if (bw == RATE_INFO_BW_20)
> -					rarpt->txrate.bw |= RATE_INFO_BW_20;
> +				if (skb->len >= offsetof(typeof(*c2h), ra_report.bw) +
> +						sizeof(c2h->ra_report.bw)) {

Today, I look up if we have a better choice, and offsetofend() can make thing simple.

if (skb->len >= offsetofend(typeof(*c2h), ra_report.bw))

Sorry for the late.

> +					if (c2h->ra_report.bw == RTL8XXXU_CHANNEL_WIDTH_40)
> +						bw = RATE_INFO_BW_40;
> +					else
> +						bw = RATE_INFO_BW_20;
> +					rarpt->txrate.bw = bw;
> +				}
>  			}
>  			bit_rate = cfg80211_calculate_bitrate(&rarpt->txrate);
>  			rarpt->bit_rate = bit_rate;
> --
> 2.38.0
> 
> ------Please consider the environment before printing this e-mail.

  reply	other threads:[~2022-11-30  0:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 19:04 [PATCH v3 1/3] wifi: rtl8xxxu: Add __packed to struct rtl8723bu_c2h Bitterblue Smith
2022-11-29 19:06 ` [PATCH v3 2/3] wifi: rtl8xxxu: Fix the channel width reporting Bitterblue Smith
2022-11-30  0:38   ` Ping-Ke Shih [this message]
2022-11-30 15:27     ` Bitterblue Smith
2022-11-29 19:07 ` [PATCH v3 3/3] wifi: rtl8xxxu: Introduce rtl8xxxu_update_ra_report Bitterblue Smith
2022-11-30 13:47   ` JunASAKA
2022-11-30 15:39     ` Bitterblue Smith
2022-12-01  1:14       ` Jun ASAKA

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=4959ded326514badbb7bbfbf60e353d4@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Jes.Sorensen@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).