From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Felix Fietkau <nbd@nbd.name>, linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT 3/4] mt76x02: do not set protection on set_rts_threshold callback
Date: Fri, 9 Nov 2018 10:23:56 +0100 [thread overview]
Message-ID: <20181109092355.GB4174@localhost.localdomain> (raw)
In-Reply-To: <1541688430-31855-4-git-send-email-sgruszka@redhat.com>
> Use set_rts_threshold calback to enable/disable threshold only for
> legacy traffic. RTS/CTS threshold for HT TXOP make make no sense
> to me since used protection (RTS/CTS , CTS-to-self or none)
> should be determined by HT capabilities and applied to any HT
> frames.
>
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> drivers/net/wireless/mediatek/mt76/mt76x02_mac.c | 16 +---------------
> drivers/net/wireless/mediatek/mt76/mt76x02_mac.h | 2 +-
> drivers/net/wireless/mediatek/mt76/mt76x02_util.c | 2 +-
> 3 files changed, 3 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/net/wireless/mediatek/mt76/mt76x02_mac.c b/drivers/net/wireless/mediatek/mt76/mt76x02_mac.c
> index 59b336e34cb5..567a7ab47fab 100644
> --- a/drivers/net/wireless/mediatek/mt76/mt76x02_mac.c
> +++ b/drivers/net/wireless/mediatek/mt76/mt76x02_mac.c
> @@ -737,7 +737,7 @@ void mt76x02_tx_complete_skb(struct mt76_dev *mdev, struct mt76_queue *q,
> }
> EXPORT_SYMBOL_GPL(mt76x02_tx_complete_skb);
>
> -void mt76x02_mac_set_tx_protection(struct mt76x02_dev *dev, u32 val)
> +void mt76x02_mac_set_rts_thresh(struct mt76x02_dev *dev, u32 val)
> {
> u32 data = 0;
>
> @@ -751,20 +751,6 @@ void mt76x02_mac_set_tx_protection(struct mt76x02_dev *dev, u32 val)
> MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
> mt76_rmw(dev, MT_OFDM_PROT_CFG,
> MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
Do we need to configure MT_OFDM_PROT_CFG and MT_CCK_PROT_CFG here? (since they
are already configured in 4/4 (mt76x02: set protection according to ht
capabilities))
> - mt76_rmw(dev, MT_MM20_PROT_CFG,
> - MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
> - mt76_rmw(dev, MT_MM40_PROT_CFG,
> - MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
> - mt76_rmw(dev, MT_GF20_PROT_CFG,
> - MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
> - mt76_rmw(dev, MT_GF40_PROT_CFG,
> - MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
> - mt76_rmw(dev, MT_TX_PROT_CFG6,
> - MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
> - mt76_rmw(dev, MT_TX_PROT_CFG7,
> - MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
> - mt76_rmw(dev, MT_TX_PROT_CFG8,
> - MT_PROT_CFG_CTRL | MT_PROT_CFG_RTS_THRESH, data);
Removing these lines we are no longer able to configure protection for VHT
rates. Do we have an equivalent for them in vht_capab?
Regards,
Lorenzo
> }
next prev parent reply other threads:[~2018-11-09 9:24 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
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 [this message]
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=20181109092355.GB4174@localhost.localdomain \
--to=lorenzo.bianconi@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.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