All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Martin Kaistra <martin.kaistra@linutronix.de>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>,
	Kalle Valo <kvalo@kernel.org>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: RE: [PATCH] wifi: rtl8xxxu: update rate mask per sta
Date: Wed, 24 Jan 2024 01:55:56 +0000	[thread overview]
Message-ID: <46aea2f4feea4f00aba0e2335f30bf76@realtek.com> (raw)
In-Reply-To: <9aadc704-48ec-4417-82fa-c5f7b19801ff@linutronix.de>



> -----Original Message-----
> From: Martin Kaistra <martin.kaistra@linutronix.de>
> Sent: Monday, January 22, 2024 5:30 PM
> To: Ping-Ke Shih <pkshih@realtek.com>; linux-wireless@vger.kernel.org
> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>; Kalle Valo <kvalo@kernel.org>; Bitterblue Smith
> <rtl8821cerfe2@gmail.com>; Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Subject: Re: [PATCH] wifi: rtl8xxxu: update rate mask per sta
> 
> Am 18.01.24 um 02:37 schrieb Ping-Ke Shih:
> >
> >
> >> -----Original Message-----
> >> From: Martin Kaistra <martin.kaistra@linutronix.de>
> >> Sent: Wednesday, January 17, 2024 10:55 PM
> >> To: linux-wireless@vger.kernel.org
> >> Cc: Jes Sorensen <Jes.Sorensen@gmail.com>; Kalle Valo <kvalo@kernel.org>; Ping-Ke Shih
> >> <pkshih@realtek.com>; Bitterblue Smith <rtl8821cerfe2@gmail.com>; Sebastian Andrzej Siewior
> >> <bigeasy@linutronix.de>
> >> +
> >> +       sta = ieee80211_find_sta_by_ifaddr(priv->hw, hdr->addr2,
> >> +                                          vif->addr);
> >
> > Can't we search for 'sta' by rx_desc->mac_id? Then, you don't need a lot of
> > code to check address.
> 
> I assume, you mean rx_desc->macid? When I try to test this, it looks to me as if
> the assignment of macid to sta in rx does not match the assignment in the driver.
> For example, I expect the first connected station to be macid 2, which is also
> sent to the firmware by report_connect, but in rxdesc it is macid 1. Can this
> even be influenced by the driver?

The rx_desc->macid is not always usable for this generation chips, so just your
original logic. 



      reply	other threads:[~2024-01-24  1:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 14:55 [PATCH] wifi: rtl8xxxu: update rate mask per sta Martin Kaistra
2024-01-18  1:37 ` Ping-Ke Shih
2024-01-22  9:30   ` Martin Kaistra
2024-01-24  1:55     ` 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=46aea2f4feea4f00aba0e2335f30bf76@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=martin.kaistra@linutronix.de \
    --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 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.