linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <tony0620emma@gmail.com>, <linux-wireless@vger.kernel.org>,
	<ku920601@realtek.com>, <phhuang@realtek.com>,
	<shaofu@realtek.com>, <steventing@realtek.com>,
	<kevin_yang@realtek.com>
Subject: Re: [PATCH 2/7] rtw88: follow the AP basic rates for tx mgmt frame
Date: Sun, 11 Apr 2021 09:21:02 +0000 (UTC)	[thread overview]
Message-ID: <20210411092102.40EE7C43461@smtp.codeaurora.org> (raw)
In-Reply-To: <20210319054218.3319-3-pkshih@realtek.com>

Ping-Ke Shih <pkshih@realtek.com> wrote:

> From: Shao-Fu Cheng <shaofu@realtek.com>
> 
> By default the driver uses the 1M and 6M rate for managemnt frames
> in 2G and 5G bands respectively. But when the basic rates is configured
> from the mac80211, we need to send the management frames according the
> basic rates.
> 
> This commit makes the driver use the lowest basic rates to send
> the management frames and a debufs entry to enable/disable force to use
> the lowest rate 1M/6M for 2.4G/5G bands.
> 
> obtain current setting
> cat /sys/kernel/debug/ieee80211/phyX/rtw88/basic_rates
> 
> force lowest rate:
> echo 1 > /sys/kernel/debug/ieee80211/phyX/rtw88/basic_rates
> 
> Signed-off-by: Shao-Fu Cheng <shaofu@realtek.com>
> Signed-off-by: Yu-Yen Ting <steventing@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>

Why is a debugfs interface needed?

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/20210319054218.3319-3-pkshih@realtek.com/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2021-04-11  9:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  5:42 [PATCH 0/7] rtw88: add some fixes and 8822c features Ping-Ke Shih
2021-03-19  5:42 ` [PATCH 1/7] rtw88: add flush hci support Ping-Ke Shih
2021-04-11  9:24   ` Kalle Valo
2021-03-19  5:42 ` [PATCH 2/7] rtw88: follow the AP basic rates for tx mgmt frame Ping-Ke Shih
2021-04-11  9:21   ` Kalle Valo [this message]
2021-04-12  8:11     ` Pkshih
2021-04-12 11:46       ` Kalle Valo
2021-04-15  4:05         ` Pkshih
2021-04-22  3:27       ` Pkshih
2021-05-19  5:59         ` Pkshih
2021-03-19  5:42 ` [PATCH 3/7] rtw88: fix DIG min setting Ping-Ke Shih
2021-03-19  5:42 ` [PATCH 4/7] rtw88: 8822c: update tx power limit table to RF v40.1 Ping-Ke Shih
2021-04-11  9:25   ` Kalle Valo
2021-03-19  5:42 ` [PATCH 5/7] rtw88: 8822c: add LC calibration for RTL8822C Ping-Ke Shih
2021-04-11  9:27   ` Kalle Valo
2021-03-19  5:42 ` [PATCH 6/7] rtw88: 8822c: add CFO tracking Ping-Ke Shih
2021-04-11  9:19   ` Kalle Valo
2021-04-12  8:11     ` Pkshih
2021-04-12 11:47       ` Kalle Valo
2021-04-15  5:02         ` Pkshih
2021-03-19  5:42 ` [PATCH 7/7] rtw88: coex: fix A2DP stutters while WL busy + WL scan Ping-Ke Shih
2021-04-11  9:28   ` Kalle Valo

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=20210411092102.40EE7C43461@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=kevin_yang@realtek.com \
    --cc=ku920601@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phhuang@realtek.com \
    --cc=pkshih@realtek.com \
    --cc=shaofu@realtek.com \
    --cc=steventing@realtek.com \
    --cc=tony0620emma@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).