From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Felix Fietkau <nbd@nbd.name>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC/RFT 2/4] mt76x02: reserve wcid 0 for global traffic
Date: Thu, 8 Nov 2018 16:54:03 +0100 [thread overview]
Message-ID: <20181108155403.GB13621@redhat.com> (raw)
In-Reply-To: <CAJ0CqmXS6zkJf3FHb5wYyPPzvqG5OBZDfcYWSjbaJY_nhcErzA@mail.gmail.com>
On Thu, Nov 08, 2018 at 04:01:54PM +0100, Lorenzo Bianconi wrote:
> > Restore behaviour on mt76x0 before commit 1bb04bb4b838 ("mt76: move
> > mt76x02_init_device in mt76x02-lib module"). This will allow to use
> > wcid 1 for AP when we work in station mode. It's not clear if this
> > is needed, but this is how vendor driver assign wcid's in STA mode.
> > This should be harmless for mt76x2.
> >
> > Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> > ---
> > drivers/net/wireless/mediatek/mt76/mt76x02_util.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/mediatek/mt76/mt76x02_util.c b/drivers/net/wireless/mediatek/mt76/mt76x02_util.c
> > index 2be4b527477f..e624397b3d8b 100644
> > --- a/drivers/net/wireless/mediatek/mt76/mt76x02_util.c
> > +++ b/drivers/net/wireless/mediatek/mt76/mt76x02_util.c
> > @@ -113,7 +113,11 @@ void mt76x02_init_device(struct mt76x02_dev *dev)
> > ieee80211_hw_set(hw, SUPPORTS_HT_CCK_RATES);
> > ieee80211_hw_set(hw, SUPPORTS_REORDERING_BUFFER);
> >
> > - dev->mt76.global_wcid.idx = 255;
> > + /* Reserve WCID 0 for mcast - thanks to this APs WCID will go to
> > + * entry no. 1 like it does in the vendor driver.
> > + */
> > + dev->mt76.wcid_mask[0] |= 1;
> > + dev->mt76.global_wcid.idx = 0;
> > dev->mt76.global_wcid.hw_key_idx = -1;
> > dev->slottime = 9;
> >
>
> Does it make any difference in AP mode?
First sta will get wcid = 1 instead of 0.
> What about using 0 instead of
> 255 for global_wcid.idx?
Patch do exactly that , it assigns:
dev->mt76.global_wcid.idx = 0;
Thanks
Stanislaw
next prev parent reply other threads:[~2018-11-08 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 14:47 [RFC/RFT 0/4] restore some old mt76x0u behaviour Stanislaw Gruszka
2018-11-08 14:47 ` [RFC/RFT 1/4] mt76x02: configure basic rates and fallback on STA mode Stanislaw Gruszka
2018-11-08 14:58 ` Lorenzo Bianconi
2018-11-08 15:52 ` Stanislaw Gruszka
2018-11-08 16:02 ` Felix Fietkau
2018-12-07 13:25 ` Stanislaw Gruszka
2018-11-08 14:47 ` [RFC/RFT 2/4] mt76x02: reserve wcid 0 for global traffic Stanislaw Gruszka
2018-11-08 15:01 ` Lorenzo Bianconi
2018-11-08 15:54 ` Stanislaw Gruszka [this message]
2018-11-08 16:05 ` Felix Fietkau
2018-11-08 14:47 ` [RFC/RFT 3/4] mt76x02: do not set protection on set_rts_threshold callback Stanislaw Gruszka
2018-11-09 9:23 ` Lorenzo Bianconi
2018-12-04 10:45 ` Stanislaw Gruszka
2018-12-04 11:50 ` Stanislaw Gruszka
2018-11-08 14:47 ` [RFC/RFT 4/4] mt76x02: set protection according to ht capabilities Stanislaw Gruszka
2018-11-09 9:29 ` Lorenzo Bianconi
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=20181108155403.GB13621@redhat.com \
--to=sgruszka@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).