From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: P Praneesh <ppranees@codeaurora.org>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH] mac80211: avoid bss color setting in non-he mode
Date: Tue, 23 Jun 2020 13:51:55 -0700 [thread overview]
Message-ID: <11461228fd45ffeb89cbd5e532d6386d@codeaurora.org> (raw)
In-Reply-To: <1592383348-19266-1-git-send-email-ppranees@codeaurora.org>
On 2020-06-17 01:42, P Praneesh wrote:
> Adding bss-color configuration for HE mode alone.
> Earlier we have enabled it by default, irrespective
> of capabilities. But bss-color feature is only for
> HE mode. Hence avoiding this by adding bss-color flag
> only for HE mode.
>
> Signed-off-by: P Praneesh <ppranees@codeaurora.org>
> ---
> net/mac80211/cfg.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/mac80211/cfg.c b/net/mac80211/cfg.c
> index 548a384..2c5847d 100644
> --- a/net/mac80211/cfg.c
> +++ b/net/mac80211/cfg.c
> @@ -992,8 +992,7 @@ static int ieee80211_start_ap(struct wiphy *wiphy,
> struct net_device *dev,
> BSS_CHANGED_P2P_PS |
> BSS_CHANGED_TXPOWER |
> BSS_CHANGED_TWT |
> - BSS_CHANGED_HE_OBSS_PD |
> - BSS_CHANGED_HE_BSS_COLOR;
> + BSS_CHANGED_HE_OBSS_PD;
>
Why not other HE flags?
> int i, err;
> int prev_beacon_int;
>
> @@ -1019,6 +1018,7 @@ static int ieee80211_start_ap(struct wiphy
> *wiphy, struct net_device *dev,
> sdata->vif.bss_conf.frame_time_rts_th =
> le32_get_bits(params->he_oper->he_oper_params,
> IEEE80211_HE_OPERATION_RTS_THRESHOLD_MASK);
> + changed |= BSS_CHANGED_HE_BSS_COLOR;
>
Praneesh,
I see that BSS color is not disabled when NL80211_ATTR_HE_BSS_COLOR is
not set.
I think this must be fixed in cfg80211.
-Rajkumar
prev parent reply other threads:[~2020-06-23 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 8:42 [PATCH] mac80211: avoid bss color setting in non-he mode P Praneesh
2020-06-23 20:51 ` Rajkumar Manoharan [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=11461228fd45ffeb89cbd5e532d6386d@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ppranees@codeaurora.org \
/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).