From: Johannes Berg <johannes@sipsolutions.net>
To: Rameshkumar Sundaram <quic_ramess@quicinc.com>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH 1/2] mac80211: add support to configure 6GHz non-ht duplicate transmission
Date: Fri, 11 Mar 2022 12:03:24 +0100 [thread overview]
Message-ID: <a517835c51a5eaf00e87fdaaef47546f70ff0d42.camel@sipsolutions.net> (raw)
In-Reply-To: <1644914581-21682-2-git-send-email-quic_ramess@quicinc.com>
Hi,
Couple of notes below:
> @@ -704,6 +704,7 @@ struct ieee80211_bss_conf {
> struct cfg80211_he_bss_color he_bss_color;
> struct ieee80211_fils_discovery fils_discovery;
> u32 unsol_bcast_probe_resp_interval;
> + bool he_6g_nonht_dup_beacon_set;
This is missing documentation.
> + cap = cfg80211_find_ext_elem(WLAN_EID_EXT_HE_OPERATION,
> + params->tail, params->tail_len);
> + if (cap && cap->datalen >= sizeof(*he_oper) + 1) {
> + he_oper = (void *)(cap->data + 1);
> + he_6ghz_oper = ieee80211_he_6ghz_oper(he_oper);
> + if (he_6ghz_oper) {
> + sdata->vif.bss_conf.he_6g_nonht_dup_beacon_set = false;
> + if (u8_get_bits(he_6ghz_oper->control,
> + IEEE80211_HE_6GHZ_OPER_CTRL_DUP_BEACON)) {
> + sdata->vif.bss_conf.he_6g_nonht_dup_beacon_set = true;
> + }
no braces needed there, and no u8_get_bits() either, you can just & ?
> + }
> + }
I am wondering though if this should even be detected from the HE
operation element itself, rather than from the beacon rate settings that
are separate in nl80211?
johannes
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-03-11 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:42 [PATCH 0/2] Add support to configure 6GHz non-ht duplicate transmission Rameshkumar Sundaram
2022-02-15 8:43 ` [PATCH 1/2] mac80211: add " Rameshkumar Sundaram
2022-03-11 11:03 ` Johannes Berg [this message]
2022-03-21 5:12 ` Rameshkumar Sundaram (QUIC)
2022-03-21 8:58 ` Johannes Berg
2022-03-22 13:50 ` Rameshkumar Sundaram (QUIC)
2022-03-22 15:04 ` Johannes Berg
2022-04-17 14:30 ` Rameshkumar Sundaram (QUIC)
2022-05-04 11:47 ` Johannes Berg
2022-02-15 8:43 ` [PATCH 2/2] ath11k: " Rameshkumar Sundaram
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=a517835c51a5eaf00e87fdaaef47546f70ff0d42.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_ramess@quicinc.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