From: Ping-Ke Shih <pkshih@realtek.com>
To: Zhen XIN <zhen.xin@nokia-sbell.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"martin.blumenstingl@googlemail.com"
<martin.blumenstingl@googlemail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [RFC -v2] wifi: rtw88: sdio: Tx status for management frames
Date: Thu, 10 Apr 2025 04:30:01 +0000 [thread overview]
Message-ID: <7f96b6ee57b44626996b70da969219b5@realtek.com> (raw)
In-Reply-To: <20250409034910.1637422-1-zhen.xin@nokia-sbell.com>
Hi Martin,
Zhen XIN <zhen.xin@nokia-sbell.com> wrote:
> Rtw88-sdio is missing the tx status report for management frames
>
> Fix this by mapping mgmt frames to queue TX_DESC_QSEL_MGMT
>
> Signed-off-by: Zhen XIN <zhen.xin@nokia-sbell.com>
> ---
> v2: have the right queue for mgmt frames as pointed out by Bitterblue Smith
> ---
> drivers/net/wireless/realtek/rtw88/sdio.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtw88/sdio.c b/drivers/net/wireless/realtek/rtw88/sdio.c
> index e024061bdbf7..4311eb7cffef 100644
> --- a/drivers/net/wireless/realtek/rtw88/sdio.c
> +++ b/drivers/net/wireless/realtek/rtw88/sdio.c
> @@ -718,10 +718,7 @@ static u8 rtw_sdio_get_tx_qsel(struct rtw_dev *rtwdev, struct sk_buff *skb,
> case RTW_TX_QUEUE_H2C:
> return TX_DESC_QSEL_H2C;
> case RTW_TX_QUEUE_MGMT:
> - if (rtw_chip_wcpu_11n(rtwdev))
> - return TX_DESC_QSEL_HIGH;
> - else
> - return TX_DESC_QSEL_MGMT;
> + return TX_DESC_QSEL_MGMT;
Do you remember why you did the special deal with 11n chips?
And this RFC looks good to me. (except to commit message, but this is RFC)
> case RTW_TX_QUEUE_HI0:
> return TX_DESC_QSEL_HIGH;
> default:
> @@ -1227,10 +1224,7 @@ static void rtw_sdio_process_tx_queue(struct rtw_dev *rtwdev,
> return;
> }
>
> - if (queue <= RTW_TX_QUEUE_VO)
> - rtw_sdio_indicate_tx_status(rtwdev, skb);
> - else
> - dev_kfree_skb_any(skb);
> + rtw_sdio_indicate_tx_status(rtwdev, skb);
> }
>
> static void rtw_sdio_tx_handler(struct work_struct *work)
> --
> 2.25.1
next prev parent reply other threads:[~2025-04-10 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 3:49 [RFC -v2] wifi: rtw88: sdio: Tx status for management frames Zhen XIN
2025-04-10 4:30 ` Ping-Ke Shih [this message]
2025-04-10 5:54 ` Martin Blumenstingl
2025-04-10 5:59 ` 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=7f96b6ee57b44626996b70da969219b5@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=zhen.xin@nokia-sbell.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