From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Shiji Yang <yangshiji66@outlook.com>
Cc: linux-wireless@vger.kernel.org,
Helmut Schaa <helmut.schaa@googlemail.com>,
Kalle Valo <kvalo@kernel.org>
Subject: Re: [PATCH V2 1/3] wifi: rt2x00: improve MT7620 register initialization
Date: Thu, 19 Oct 2023 19:55:51 +0200 [thread overview]
Message-ID: <20231019175551.GB512047@wp.pl> (raw)
In-Reply-To: <TYAP286MB031553CCD4B7A3B89C85935DBCD4A@TYAP286MB0315.JPNP286.PROD.OUTLOOK.COM>
On Thu, Oct 19, 2023 at 07:58:56PM +0800, Shiji Yang wrote:
> 1. Do not hard reset the BBP. We can use soft reset instead. This
> change has some help to the calibration failure issue.
> 2. Enable falling back to legacy rate from the HT/RTS rate by
> setting the HT_FBK_TO_LEGACY register.
> 3. Implement MCS rate specific maximum PSDU size. It can improve
> the transmission quality under the low RSSI condition.
> 4. Set BBP_84 register value to 0x19. This is used for extension
> channel overlapping IOT.
>
> Signed-off-by: Shiji Yang <yangshiji66@outlook.com>
Acked-by: Stanislaw Gruszka <stf_xl@wp.pl>
next prev parent reply other threads:[~2023-10-19 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231019115859.2791-1-yangshiji66@outlook.com>
2023-10-19 11:58 ` [PATCH V2 1/3] wifi: rt2x00: improve MT7620 register initialization Shiji Yang
2023-10-19 17:55 ` Stanislaw Gruszka [this message]
2023-10-25 9:07 ` Kalle Valo
2023-10-19 11:58 ` [PATCH V2 2/3] wifi: rt2x00: rework MT7620 channel config function Shiji Yang
2023-10-19 18:03 ` Stanislaw Gruszka
2023-10-19 11:58 ` [PATCH V2 3/3] wifi: rt2x00: rework MT7620 PA/LNA RF calibration Shiji Yang
2023-10-19 18:03 ` Stanislaw Gruszka
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=20231019175551.GB512047@wp.pl \
--to=stf_xl@wp.pl \
--cc=helmut.schaa@googlemail.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yangshiji66@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;
as well as URLs for NNTP newsgroup(s).