public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: Ryder Lee <Ryder.Lee@mediatek.com>
To: "kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"lorenzo.bianconi@redhat.com" <lorenzo.bianconi@redhat.com>,
	"nbd@nbd.name" <nbd@nbd.name>,
	"Shayne Chen (陳軒丞)" <Shayne.Chen@mediatek.com>,
	"Evelyn Tsai (蔡珊鈺)" <Evelyn.Tsai@mediatek.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] wifi: mt76: mt7915: enable BSS_CHANGED_MU_GROUPS support
Date: Thu, 3 Aug 2023 06:58:01 +0000	[thread overview]
Message-ID: <ec7643c5d10b3cee3bbcd893cb08dccdecfffa6f.camel@mediatek.com> (raw)
In-Reply-To: <87bkfozpr4.fsf@kernel.org>

On Thu, 2023-08-03 at 07:58 +0300, Kalle Valo wrote:
>  	 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>  Ryder Lee <ryder.lee@mediatek.com> writes:
> 
> > The Group ID Management frame is an Action frame of category VHT.
> > It is transmitted by the AP to assign or change the user position
> > of a STA for one or more group IDs.
> >
> > Also, sniffer can use a given group id to monitor STA that belongs
> > to that group.
> >
> > Notify underlying driver of changes via BSS_CHANGED_MU_GROUPS.
> >
> > Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
> > Change-Id: I3d2f5508a2b6eb7c929c3997c31a9285713c8bea
> 
> No Change-Id, please.
> 
ok.

> > --- a/drivers/net/wireless/mediatek/mt76/mt7915/main.c
> > +++ b/drivers/net/wireless/mediatek/mt76/mt7915/main.c
> > @@ -593,6 +593,34 @@ mt7915_update_bss_color(struct ieee80211_hw
> *hw,
> >  	}
> >  }
> >  
> > +static void
> > +mt7915_update_mu_group(struct ieee80211_hw *hw, struct
> ieee80211_vif *vif,
> > +		       struct ieee80211_bss_conf *info)
> > +{
> > +	struct mt7915_phy *phy = mt7915_hw_phy(hw);
> > +	struct mt7915_dev *dev = mt7915_hw_dev(hw);
> > +	u8 i, band = phy->mt76->band_idx;
> > +	u32 *mu;
> > +
> > +	mu = (u32 *)info->mu_group.membership;
> 
> Is this safe on big endian?
> 

hmmm, I'm thinking about this. Doesn't this byte array covert (and
then write) to the same cpu endianess?

__le32 mu = (__le32 *)info->mu_group.membership
write(..., le32_to_cpu(mu));
I know something like above change is safe, but just checking...

RYder

      reply	other threads:[~2023-08-03  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 18:49 [PATCH] wifi: mt76: mt7915: enable BSS_CHANGED_MU_GROUPS support Ryder Lee
2023-08-03  4:58 ` Kalle Valo
2023-08-03  6:58   ` Ryder Lee [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=ec7643c5d10b3cee3bbcd893cb08dccdecfffa6f.camel@mediatek.com \
    --to=ryder.lee@mediatek.com \
    --cc=Evelyn.Tsai@mediatek.com \
    --cc=Shayne.Chen@mediatek.com \
    --cc=kvalo@kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=nbd@nbd.name \
    /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