Sync with wireless-next.git include/uapi/linux/nl80211.h
This brings in nl80211 definitions as of 2023-03-30. Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
302d761a85
commit
921f82cf18
1 changed files with 23 additions and 1 deletions
|
@ -2794,6 +2794,17 @@ enum nl80211_commands {
|
|||
* @NL80211_ATTR_HW_TIMESTAMP_ENABLED: Indicates whether HW timestamping should
|
||||
* be enabled or not (flag attribute).
|
||||
*
|
||||
* @NL80211_ATTR_EMA_RNR_ELEMS: Optional nested attribute for
|
||||
* reduced neighbor report (RNR) elements. This attribute can be used
|
||||
* only when NL80211_MBSSID_CONFIG_ATTR_EMA is enabled.
|
||||
* Userspace is responsible for splitting the RNR into multiple
|
||||
* elements such that each element excludes the non-transmitting
|
||||
* profiles already included in the MBSSID element
|
||||
* (%NL80211_ATTR_MBSSID_ELEMS) at the same index. Each EMA beacon
|
||||
* will be generated by adding MBSSID and RNR elements at the same
|
||||
* index. If the userspace includes more RNR elements than number of
|
||||
* MBSSID elements then these will be added in every EMA beacon.
|
||||
*
|
||||
* @NUM_NL80211_ATTR: total number of nl80211_attrs available
|
||||
* @NL80211_ATTR_MAX: highest attribute number currently defined
|
||||
* @__NL80211_ATTR_AFTER_LAST: internal use
|
||||
|
@ -3328,6 +3339,8 @@ enum nl80211_attrs {
|
|||
NL80211_ATTR_MAX_HW_TIMESTAMP_PEERS,
|
||||
NL80211_ATTR_HW_TIMESTAMP_ENABLED,
|
||||
|
||||
NL80211_ATTR_EMA_RNR_ELEMS,
|
||||
|
||||
/* add attributes here, update the policy in nl80211.c */
|
||||
|
||||
__NL80211_ATTR_AFTER_LAST,
|
||||
|
@ -4048,6 +4061,10 @@ enum nl80211_band_iftype_attr {
|
|||
* @NL80211_BAND_ATTR_EDMG_BW_CONFIG: Channel BW Configuration subfield encodes
|
||||
* the allowed channel bandwidth configurations.
|
||||
* Defined by IEEE P802.11ay/D4.0 section 9.4.2.251, Table 13.
|
||||
* @NL80211_BAND_ATTR_S1G_MCS_NSS_SET: S1G capabilities, supported S1G-MCS and NSS
|
||||
* set subfield, as in the S1G information IE, 5 bytes
|
||||
* @NL80211_BAND_ATTR_S1G_CAPA: S1G capabilities information subfield as in the
|
||||
* S1G information IE, 10 bytes
|
||||
* @NL80211_BAND_ATTR_MAX: highest band attribute currently defined
|
||||
* @__NL80211_BAND_ATTR_AFTER_LAST: internal use
|
||||
*/
|
||||
|
@ -4068,6 +4085,9 @@ enum nl80211_band_attr {
|
|||
NL80211_BAND_ATTR_EDMG_CHANNELS,
|
||||
NL80211_BAND_ATTR_EDMG_BW_CONFIG,
|
||||
|
||||
NL80211_BAND_ATTR_S1G_MCS_NSS_SET,
|
||||
NL80211_BAND_ATTR_S1G_CAPA,
|
||||
|
||||
/* keep last */
|
||||
__NL80211_BAND_ATTR_AFTER_LAST,
|
||||
NL80211_BAND_ATTR_MAX = __NL80211_BAND_ATTR_AFTER_LAST - 1
|
||||
|
@ -6544,7 +6564,9 @@ enum nl80211_timeout_reason {
|
|||
* channels on which APs are expected to be found. Note that when not set,
|
||||
* the scan logic would scan all 6GHz channels, but since transmission of
|
||||
* probe requests on non PSC channels is limited, it is highly likely that
|
||||
* these channels would passively be scanned.
|
||||
* these channels would passively be scanned. Also note that when the flag
|
||||
* is set, in addition to the colocated APs, PSC channels would also be
|
||||
* scanned if the user space has asked for it.
|
||||
*/
|
||||
enum nl80211_scan_flags {
|
||||
NL80211_SCAN_FLAG_LOW_PRIORITY = 1<<0,
|
||||
|
|
Loading…
Reference in a new issue