All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "Marcin Ślusarz" <marcin.slusarz@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "Marcin Ślusarz" <mslusarz@renau.com>,
	"Bernie Huang" <phhuang@realtek.com>,
	"Kalle Valo" <kvalo@kernel.org>
Subject: RE: [PATCH] wifi: rtw88: usb: unbreak multicast
Date: Mon, 17 Jun 2024 01:20:48 +0000	[thread overview]
Message-ID: <44061283fd014cbc898a382ed5c3c26b@realtek.com> (raw)
In-Reply-To: <20240614102835.518348-1-mslusarz@renau.com>

Marcin Ślusarz <marcin.slusarz@gmail.com> wrote:
> 
> High queue is not functioning, for some reason.
> Broken by 076f786a0ae14a81f40314b96a2d815e264bc213

Pointing out 076f786a0ae1 ("wifi: rtw88: Fix AP mode incorrect DTIM behavior")
would be clearer. Please also mentioned the chip you are using. 

> 
> Signed-off-by: Marcin Ślusarz <mslusarz@renau.com>
> Cc: Po-Hao Huang <phhuang@realtek.com>
> Cc: Ping-Ke Shih <pkshih@realtek.com>
> Cc: Kalle Valo <kvalo@kernel.org>
> ---
>  drivers/net/wireless/realtek/rtw88/usb.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/drivers/net/wireless/realtek/rtw88/usb.c b/drivers/net/wireless/realtek/rtw88/usb.c
> index c25fd4b193a7..aacc5a105b15 100644
> --- a/drivers/net/wireless/realtek/rtw88/usb.c
> +++ b/drivers/net/wireless/realtek/rtw88/usb.c
> @@ -492,9 +492,6 @@ static u8 rtw_usb_tx_queue_mapping_to_qsel(struct sk_buff *skb)
> 
>         if (unlikely(ieee80211_is_mgmt(fc) || ieee80211_is_ctl(fc)))
>                 qsel = TX_DESC_QSEL_MGMT;
> -       else if (is_broadcast_ether_addr(hdr->addr1) ||
> -                is_multicast_ether_addr(hdr->addr1))
> -               qsel = TX_DESC_QSEL_HIGH;

I think broadcast/multicast packets should go via HIGH queue is correct, but
somehow registers aren't configured correctly. Bernie (you have CC'ed) will
help to check registers. 


>         else if (skb_get_queue_mapping(skb) <= IEEE80211_AC_BK)
>                 qsel = skb->priority;
>         else
> --
> 2.25.1


  reply	other threads:[~2024-06-17  1:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 15:05 rtw88 multicast failure in AP mode Marcin Ślusarz
2024-06-11  2:32 ` Ping-Ke Shih
2024-06-11 11:10   ` Marcin Ślusarz
2024-06-12  1:30     ` Ping-Ke Shih
2024-06-12  5:55       ` Marcin Ślusarz
2024-06-12  6:08         ` Ping-Ke Shih
2024-06-12  6:59           ` Marcin Ślusarz
2024-06-12 15:24             ` Marcin Ślusarz
2024-06-14 10:28               ` [PATCH] wifi: rtw88: usb: unbreak multicast Marcin Ślusarz
2024-06-17  1:20                 ` Ping-Ke Shih [this message]
2024-07-30  7:40                 ` 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=44061283fd014cbc898a382ed5c3c26b@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=mslusarz@renau.com \
    --cc=phhuang@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.