linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Andrey Skvortsov <andrej.skvortzov@gmail.com>,
	Kalle Valo <kvalo@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	Fiona Klute <fiona.klute@gmx.de>
Subject: RE: [PATCH v2 2/2] wifi: rtw88: enable TX reports for the management queue
Date: Thu, 10 Jul 2025 04:50:17 +0000	[thread overview]
Message-ID: <65e152e2d7ea403eafeaff9e4817d29f@realtek.com> (raw)
In-Reply-To: <20250709223159.2787192-3-andrej.skvortzov@gmail.com>

Andrey Skvortsov <andrej.skvortzov@gmail.com> wrote:
> This is needed for AP mode. Otherwise client sees the network, but
> can't connect to it.
> 
> REG_FWHW_TXQ_CTRL+1 is set to WLAN_TXQ_RPT_EN (0x1F) in common mac
> init function (__rtw8723x_mac_init), but the value was overwritten
> from mac table later. mac_postinit is run after registers from mac
> table are set, this allows to set correct values.
> 
> Tested on rtl8723cs, that reuses rtw8703b driver.
> 
> Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
> ---
>  drivers/net/wireless/realtek/rtw88/rtw8703b.c | 1 +
>  drivers/net/wireless/realtek/rtw88/rtw8723d.c | 1 +
>  drivers/net/wireless/realtek/rtw88/rtw8723x.c | 9 ++++++++-
>  drivers/net/wireless/realtek/rtw88/rtw8723x.h | 6 ++++++
>  4 files changed, 16 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/wireless/realtek/rtw88/rtw8703b.c
> b/drivers/net/wireless/realtek/rtw88/rtw8703b.c
> index 03475af973b52..821c28d9cb5d4 100644
> --- a/drivers/net/wireless/realtek/rtw88/rtw8703b.c
> +++ b/drivers/net/wireless/realtek/rtw88/rtw8703b.c
> @@ -1832,6 +1832,7 @@ static const struct rtw_chip_ops rtw8703b_ops = {
>         .power_on               = rtw_power_on,
>         .power_off              = rtw_power_off,
>         .mac_init               = rtw8723x_mac_init,
> +       .mac_postinit           = rtw8723x_mac_postinit,

If chips don't have this ops, please give them NULL to be clear that
we don't miss it.

Since these two patches are small, I don't mind to combine them together.
Make decision yourself.

By the way, please select rtw-next tree by [PATCH v3 rtw-next].

>         .dump_fw_crash          = NULL,
>         .shutdown               = NULL,
>         .read_efuse             = rtw8703b_read_efuse,

[...]


      reply	other threads:[~2025-07-10  4:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 22:31 [PATCH v2 0/2] wifi: rtw88: enable TX reports for the management queue Andrey Skvortsov
2025-07-09 22:31 ` [PATCH v2 1/2] wifi: rtw88: introduce callback to override phy parameters from tables Andrey Skvortsov
2025-07-10  4:46   ` Ping-Ke Shih
2025-07-10 23:17   ` kernel test robot
2025-07-09 22:31 ` [PATCH v2 2/2] wifi: rtw88: enable TX reports for the management queue Andrey Skvortsov
2025-07-10  4:50   ` Ping-Ke Shih [this message]

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=65e152e2d7ea403eafeaff9e4817d29f@realtek.com \
    --to=pkshih@realtek.com \
    --cc=andrej.skvortzov@gmail.com \
    --cc=fiona.klute@gmx.de \
    --cc=kvalo@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).