STRUCT CFG80211_PMSR_CAPABILITIES(9)

💖 NAME 💖

struct cfg80211_pmsr_capabilities — the cfg80211 peer measurement capabilities 💅 (yes that's the whole name, it's a mouthful, we know)

---

✨ SYNOPSIS ✨

okay so here's the whole struct, look at her, she's gorgeous:

struct cfg80211_pmsr_capabilities {
    unsigned int max_peers;
    u8 report_ap_tsf:1, randomize_mac_addr:1;
    struct {
      u32 preambles;
      u32 bandwidths;
      s8 max_bursts_exponent;
      u8 max_ftms_per_burst;
      u8 supported:1, asap:1, non_asap:1, request_lci:1,
         request_civicloc:1, trigger_based:1, non_trigger_based:1,
         support_6ghz:1;
      u8 max_tx_ltf_rep;
      u8 max_rx_ltf_rep;
      u8 max_tx_sts;
      u8 max_rx_sts;
      u8 max_total_ltf_tx;
      u8 max_total_ltf_rx;
      struct {
        u8 support_ntb:1, support_tb:1, support_edca:1;
        u32 max_peers;
      } ista;
      struct {
        u8 support_ntb:1, support_tb:1, support_edca:1;
        u32 max_peers;
      } rsta;
      u8 max_no_of_tx_antennas;
      u8 max_no_of_rx_antennas;
      u32 min_allowed_ranging_interval_edca;
      u32 min_allowed_ranging_interval_ntb;
      struct {
        u8 infra_support:1, pd_support:1;
      } type;
      u8 concurrent_ista_rsta_support:1;
      u32 pd_preambles;
      u32 pd_bandwidths;
    } ftm;
};

---

🧚 MEMBERS 🧚

bestie this is the part where we go field by field, stay with me 💜

• max_peers — the maximum number of peers you can have in a single measurement. like a group chat with a member cap, no cap 🫶
• report_ap_tsf — can it report the assoc AP's TSF for radio resource measurement? that's the vibe check on this one.
• randomize_mac_addr — can randomize the MAC address for the measurement. yes ma'am, privacy queen 👑
• ftm — all the FTM measurement data lives in here, this is the main character of the struct ngl

---

🌸 the ftm era 🌸

• ftm.preambles — bitmap of preambles supported (enum nl80211_preamble). it's giving bitmask energy ✨
• ftm.bandwidths — bitmap of bandwidths supported (enum nl80211_chan_width)
• ftm.max_bursts_exponent — maximum burst exponent supported, and it's a s8 for a reason: set to -1 if not limited. > ⚠️ heads up babes: setting this will necessarily forbid using the value 15 to let the responder pick. that's not me being dramatic, that's just what it says 😭
• ftm.max_ftms_per_burst — maximum FTMs per burst supported (set to 0 if not limited). zero means go off, no ceiling 🦋
• ftm.supported — FTM measurement is supported. that's it, that's the flag 💅
• ftm.asap — ASAP-mode is supported. do it now energy.
• ftm.non_asap — non-ASAP-mode is supported. do it eventually energy.
• ftm.request_lci — can request LCI data
• ftm.request_civicloc — can request civic location data
• ftm.trigger_based — trigger based ranging measurement is supported
• ftm.non_trigger_based — non trigger based ranging measurement is supported
• ftm.support_6ghz — supports ranging in the 6 GHz band. highkey iconic spectrum 🌈

---

⭐ the LTF/STS section (yes there are a lot of these) ⭐

• ftm.max_tx_ltf_rep — maximum number of TX LTF repetitions supported (0 means only one LTF, no repetitions)
• ftm.max_rx_ltf_rep — maximum number of RX LTF repetitions supported (0 means only one LTF, no repetitions)
• ftm.max_tx_sts — maximum number of TX STS supported (zero based). zero based, don't forget, that detail matters fr fr
• ftm.max_rx_sts — maximum number of RX STS supported (zero based)
• ftm.max_total_ltf_tx — maximum total number of LTFs that can be transmitted (0 means unknown)
• ftm.max_total_ltf_rx — maximum total number of LTFs that can be received (0 means unknown)

---

🎀 roles: ista & rsta 🎀

• ftm.ista — initiator role capabilities
• ftm.ista.support_ntb — supports operating as ISTA in PMSR FTM request for NTB ranging.
• ftm.ista.support_tb — supports operating as ISTA in PMSR FTM request for TB ranging.
• ftm.ista.support_edca — supports operating as ISTA in PMSR FTM request for EDCA based ranging.
• ftm.ista.max_peers — maximum number of peers supported in the ISTA role. If zero, no role-specific peer limit applies. (so 0 = unlimited-ish, cute)
• ftm.rsta — responder role capabilities
• ftm.rsta.support_ntb — supports operating as RSTA in PMSR FTM request for NTB ranging.
• ftm.rsta.support_tb — supports operating as RSTA in PMSR FTM request for TB ranging.
• ftm.rsta.support_edca — supports operating as RSTA in PMSR FTM request for EDCA based ranging.
• ftm.rsta.max_peers — maximum number of peers supported in the RSTA role. If zero, no role-specific peer limit applies.

---

🦋 antennas & intervals 🦋

• ftm.max_no_of_tx_antennas — maximum number of transmit antennas supported for EDCA based ranging (0 means unknown)
• ftm.max_no_of_rx_antennas — maximum number of receive antennas supported for EDCA based ranging (0 means unknown)
• ftm.min_allowed_ranging_interval_edca — Minimum EDCA ranging interval supported by the device, in milli seconds (0 means unknown). Applications can use this value to estimate the burst period to be given in the FTM request for the EDCA based ranging case. If non-zero, this value will be used to validate the burst period in the FTM request. so like, it's not just decor, it does actual work 💀
• ftm.min_allowed_ranging_interval_ntb — Minimum NTB ranging interval supported by the device, in milli seconds (0 means unknown). Applications can use this value to estimate the burst period to be given in the FTM request for the NTB ranging case. If non-zero, this value will be used to validate the nominal time in the FTM request. (yes NTB validates the nominal time, EDCA validates the burst period — they're different, don't mix them up 🍓)

---

🌈 the ftm.type moment 🌈

• ftm.type — ranging type capabilities
• ftm.type.infra_support — supports infrastructure ranging (STA-to-AP or AP-to-STA) as part of Proximity Detection
• ftm.type.pd_support — supports peer-to-peer ranging as mentioned in the specification "PR Implementation Consideration Draft 1.9 rev 1" where PD stands for proximity detection. ok quote the spec exactly, we don't freelance 📜

---

💀 PD extras & the concurrent thing 💀

• ftm.concurrent_ista_rsta_support — indicates if the device can simultaneously act as initiator and responder in a multi-peer measurement request. > ⚠️ Only valid if ftm.rsta_support is set. (yes, read that again, that's exactly what it says — we do not editorialize 💅)
• ftm.pd_preambles — bitmap of preambles supported (enum nl80211_preamble) for PD ranging requests. Ignored if ftm.type.pd_support is not set.
• ftm.pd_bandwidths — bitmap of bandwidths supported (enum nl80211_chan_width) for PD ranging requests. Ignored if ftm.type.pd_support is not set.

---

okay that's the struct unpacked, and there's still more coming so don't go anywhere 💖

🦋 SEE ALSO 🦋

okay bestie, deep breath — this is the part where the page stops explaining and just flexes. It's a whole constellation of cross-references, and yes, we're gonna get through all of them, because every single one is here for a reason. Buckle in, grab a snack 🍓.

• Kernel file ./include/net/cfg80211.h — that's the actual file this struct lives in. Home sweet home 🏠

---

🌸 The channel / rate / cap family (the OGs)

• Introduction(9), Device registration(9), enum ieee80211_channel_flags(9), struct ieee80211_channel(9), enum ieee80211_rate_flags(9), enum ieee80211_bss_type(9), enum ieee80211_privacy(9), struct ieee80211_rate(9) — the absolute basics. Channels, rates, BSS types, privacy. Start here if you're new, no cap ✨
• struct ieee80211_he_obss_pd(9), struct cfg80211_he_bss_color(9), struct ieee80211_sta_ht_cap(9), struct ieee80211_sta_vht_cap(9), struct ieee80211_sta_he_cap(9), struct ieee80211_eht_mcs_nss_supp(9), struct ieee80211_sta_eht_cap(9), struct ieee80211_sta_uhr_cap(9) — the capability glow-up timeline, HT → VHT → HE → EHT → UHR. It's giving generational excellence 💅
• struct ieee80211_sband_iftype_data(9), enum ieee80211_edmg_bw_config(9), struct ieee80211_edmg(9), struct ieee80211_sta_s1g_cap(9), struct ieee80211_supported_band(9) — per-band, per-iftype data plus the EDMG and S1G corner of the universe 🦋
• _ieee80211_set_sband_iftype_data(9) — note the leading underscore, bestie, that's not a typo, copy it exactly 🙈
• ieee80211_set_sband_iftype_data(9), for_each_sband_iftype_data(9), ieee80211_get_sband_iftype_data(9), ieee80211_get_he_iftype_cap(9), ieee80211_get_he_6ghz_capa(9), ieee80211_get_eht_iftype_cap(9), ieee80211_get_uhr_iftype_cap(9) — setters, getters and the iterator. Iconic little helper squad 🫶
• wiphy_read_of_freq_limits(9) — pulls freq limits out of device tree. 🎀

---

🔥 Actions and configuration (aka the whole entire world)

• Actions and configuration(9), struct vif_params(9), struct key_params(9), struct cfg80211_chan_def(9), struct cfg80211_tid_cfg(9), struct cfg80211_tid_config(9), struct cfg80211_fils_aad(9), struct cfg80211_set_hw_timestamp(9) — the entry point plus the parameter structs you'll bump into immediately. 🧚

the chandef cinematic universe

• cfg80211_get_chandef_type(9), cfg80211_chandef_create(9), cfg80211_chandef_identical(9), cfg80211_chandef_is_edmg(9), cfg80211_chandef_is_s1g(9), cfg80211_chandef_compatible(9), nl80211_chan_width_to_mhz(9), cfg80211_chandef_get_width(9), cfg80211_chandef_valid(9), cfg80211_chandef_usable(9) — build it, check it, compare it, measure it. The chandef main character arc 👑
• cfg80211_chandef_dfs_required(9), cfg80211_chandef_dfs_usable(9), cfg80211_chandef_dfs_cac_time(9), cfg80211_chandef_primary(9), cfg80211_chandef_npca_valid(9), cfg80211_chandef_add_npca(9), cfg80211_chandef_add_dbe(9), nl80211_send_chandef(9), ieee80211_chandef_max_power(9), cfg80211_chandef_s1g_pri_width(9), cfg80211_any_usable_channels(9) — DFS duties, primary channel, NPCA, DBE, sending it out over nl80211, power, S1G width, and the "is anything usable" check 😭

structs for days

• enum survey_info_flags(9), struct survey_info(9), struct cfg80211_crypto_settings(9), struct cfg80211_mbssid_config(9), struct cfg80211_mbssid_elems(9), struct cfg80211_rnr_elems(9), struct cfg80211_beacon_data(9), struct cfg80211_acl_data(9), struct cfg80211_fils_discovery(9), struct cfg80211_unsol_bcast_probe_resp(9), struct cfg80211_s1g_short_beacon(9), struct cfg80211_ap_settings(9), struct cfg80211_ap_update(9), struct cfg80211_csa_settings(9), struct cfg80211_color_change_settings(9), struct iface_combination_params(9) — survey, crypto, multi-BSSID, RNR, beacon data, ACL, FILS discovery, unsolicited broadcast probe response, S1G short beacon, AP settings/update, CSA, color change, iface combos. That's a lot of structs and every single one is valid 💖

stations, links & rates

• enum station_parameters_apply_mask(9), struct sta_txpwr(9), struct link_station_parameters(9), struct link_station_del_parameters(9), struct cfg80211_ttlm_params(9), struct station_parameters(9), struct station_del_parameters(9), enum cfg80211_station_type(9), cfg80211_check_station_change(9) — add a station, delete a station, TTLM params, and the change-checker that keeps you honest 🫡
• enum rate_info_flags(9), enum rate_info_bw(9), struct rate_info(9), enum bss_param_flags(9), struct sta_bss_parameters(9), struct cfg80211_txq_stats(9), struct cfg80211_tid_stats(9), struct link_station_info(9), struct station_info(9) — rates, BSS params, txq/TID stats, per-link and overall station info. Stats girlies rise 🌈
• struct cfg80211_sar_sub_specs(9), struct cfg80211_sar_specs(9), struct cfg80211_sar_freq_ranges(9), struct cfg80211_sar_capa(9), cfg80211_get_station(9), enum monitor_flags(9), enum mpath_info_flags(9), struct mpath_info(9), enum wiphy_bss_param_flags(9), struct bss_parameters(9), struct mesh_config(9), struct mesh_setup(9), struct ocb_setup(9), struct ieee80211_txq_params(9) — SAR specs, station lookup, monitor flags, mesh path info, BSS params, mesh config/setup, OCB setup, txq params. Mesh girlies, this one's for you 🧚‍♀️

---

⭐ Scanning and BSS list handling

• Scanning and BSS list handling(9), struct cfg80211_ssid(9), struct cfg80211_scan_info(9), struct cfg80211_scan_6ghz_params(9), struct cfg80211_scan_request(9), struct cfg80211_match_set(9), struct cfg80211_sched_scan_plan(9), struct cfg80211_bss_select_adjust(9), struct cfg80211_sched_scan_request(9), enum cfg80211_signal_type(9), struct cfg80211_inform_bss(9), struct cfg80211_bss_ies(9), struct cfg80211_bss(9), ieee80211_bss_get_elem(9), ieee80211_bss_get_ie(9) — scanning, scheduled scanning, 6GHz params, BSS selection tweaks, signal types, IEs and BSS lookups. The scan arc is SO iconic ✨

connections & powersave

• struct cfg80211_auth_request(9), struct cfg80211_assoc_link(9), struct cfg80211_ml_reconf_req(9), enum cfg80211_assoc_req_flags(9), struct cfg80211_assoc_request(9), struct cfg80211_deauth_request(9), struct cfg80211_disassoc_request(9), struct cfg80211_ibss_params(9), struct cfg80211_bss_selection(9), struct cfg80211_connect_params(9), enum cfg80211_connect_params_changed(9), enum wiphy_params_flags(9), struct cfg80211_pmksa(9) — auth, assoc, ML reconf, deauth, disassoc, IBSS, BSS selection, connect params, PMKSA. The whole relationship lifecycle, honestly 💀
• struct cfg80211_pkt_pattern(9), struct cfg80211_wowlan_tcp(9), struct cfg80211_wowlan(9), struct cfg80211_coalesce_rules(9), struct cfg80211_coalesce(9), struct cfg80211_wowlan_nd_match(9), struct cfg80211_wowlan_nd_info(9), struct cfg80211_wowlan_wakeup(9), struct cfg80211_gtk_rekey_data(9), struct cfg80211_update_ft_ies_params(9), struct cfg80211_mgmt_tx_params(9), struct cfg80211_dscp_exception(9), struct cfg80211_dscp_range(9), struct cfg80211_qos_map(9) — wowlan (packet patterns, TCP keepalive, net-detect), coalesce rules, GTK rekey, FT IEs, mgmt TX params, DSCP exceptions/ranges and the QoS map. Sleep-mode excellence 😴

---

🎀 Neighbor Awareness Networking (NAN) — and honestly so much more

• Neighbor Awareness Networking (NAN)(9), struct cfg80211_nan_band_config(9), struct cfg80211_nan_conf(9), struct cfg80211_nan_channel(9), struct cfg80211_nan_local_sched(9), struct cfg80211_nan_peer_map(9), struct cfg80211_nan_peer_sched(9), enum cfg80211_nan_conf_changes(9), struct cfg80211_nan_func_filter(9), struct cfg80211_nan_func(9) — NAN config, channels, local/peer schedules, peer maps, filters, functions. NAN stans assemble 🦋
• struct cfg80211_pmk_conf(9), struct cfg80211_external_auth_params(9), struct cfg80211_ftm_responder_stats(9), struct cfg80211_pmsr_ftm_result(9), struct cfg80211_pmsr_result(9), struct cfg80211_pmsr_ftm_request_peer(9), struct cfg80211_pmsr_request_peer(9), struct cfg80211_pmsr_request(9), struct cfg80211_update_owe_info(9), struct mgmt_frame_regs(9) — PMK conf, external auth, FTM responder stats, and look — the whole cfg80211_pmsr_* result/request family that this very page is about. Full circle moment 🔥

wiphy-adjacent everything

• struct cfg80211_ops(9), enum wiphy_flags(9), struct ieee80211_iface_limit(9), struct ieee80211_iface_combination(9), enum wiphy_wowlan_support_flags(9), struct wiphy_wowlan_support(9), struct wiphy_coalesce_support(9), enum wiphy_vendor_command_flags(9), enum wiphy_opmode_flag(9), struct sta_opmode_info(9), struct wiphy_vendor_command(9), struct wiphy_iftype_ext_capab(9), cfg80211_get_iftype_ext_capa(9), struct wiphy_iftype_akm_suites(9), struct wiphy_radio_cfg(9), struct wiphy_radio_freq_range(9), struct wiphy_radio(9), enum wiphy_nan_flags(9), struct wiphy_nan_capa(9), struct wiphy(9) — ops, flags, iface limits/combinations, wowlan/coalesce support, vendor command bits, opmode, ext capabs, AKM suites, radio config/freq ranges, NAN flags & capa, and the big one: struct wiphy(9) 👑
• wiphy_priv(9), priv_to_wiphy(9), set_wiphy_dev(9), wiphy_dev(9), wiphy_name(9), wiphy_new_nm(9), wiphy_new(9), wiphy_register(9), rcu_dereference_wiphy(9), wiphy_dereference(9), get_wiphy_regdom(9), wiphy_unregister(9), wiphy_free(9), wiphy_lock(9), wiphy_unlock(9) — private data juggling, dev/name accessors, allocate, register, RCU deref helpers, regdom, unregister, free, lock/unlock. The full wiphy lifecycle, start to finish 💅
• wiphy_work_queue(9), wiphy_work_cancel(9), wiphy_work_flush(9), wiphy_delayed_work_queue(9), wiphy_delayed_work_cancel(9), wiphy_delayed_work_flush(9), wiphy_delayed_work_pending(9), wiphy_hrtimer_work_queue(9), wiphy_hrtimer_work_cancel(9), wiphy_hrtimer_work_flush(9), wiphy_hrtimer_work_pending(9) — queue it, cancel it, flush it, check if it's pending. Regular work, delayed work, hrtimer work — all three flavours, all accounted for 🫶
• enum ieee80211_ap_reg_power(9), struct wireless_dev(9), wdev_priv(9), wdev_chandef(9) — AP regulatory power, and then the wdev trio: priv, and chandef 🌸

---

🌈 Utility functions

• Utility functions(9), ieee80211_channel_equal(9), ieee80211_channel_to_khz(9), ieee80211_channel_to_freq_khz(9), ieee80211_channel_to_frequency(9), ieee80211_freq_khz_to_channel(9), ieee80211_frequency_to_channel(9), ieee80211_get_channel_khz(9), ieee80211_get_channel(9), cfg80211_channel_is_psc(9), ieee80211_radio_freq_range_valid(9), cfg80211_radio_chandef_valid(9), cfg80211_wdev_channel_allowed(9) — compare channels, convert channel↔freq in both kHz and the classic way, look channels up, check PSC, validate freq ranges and chandefs, check if a wdev is allowed on a channel. Conversion slay ⭐
• ieee80211_get_response_rate(9), ieee80211_mandatory_rates(9), struct ieee80211_radiotap_iterator(9), ieee80211_get_hdrlen_from_skb(9), ieee80211_hdrlen(9), ieee80211_get_mesh_hdrlen(9) — response/mandatory rates, radiotap iteration, and the header-length trio (from skb, plain, and mesh). 📏

---

💜 Data path helpers

• Data path helpers(9), ieee80211_data_to_8023_exthdr(9), ieee80211_data_to_8023(9), ieee80211_is_valid_amsdu(9), ieee80211_amsdu_to_8023s(9), ieee80211_get_8023_tunnel_proto(9), ieee80211_strip_8023_mesh_hdr(9), cfg80211_classify8021d(9), cfg80211_find_elem_match(9), cfg80211_find_ie_match(9), cfg80211_find_elem(9), cfg80211_find_ie(9), cfg80211_find_ext_elem(9), cfg80211_find_ext_ie(9), cfg80211_find_vendor_elem(9), cfg80211_find_vendor_ie(9) — 802.11→802.3 conversion (plus the exthdr version), AMSDU validation/conversion, tunnel proto, mesh header stripping, 802.1d classification, and the whole find-an-element squad (match, plain, ext, vendor — elem and ie variants of each) 🔍
• enum cfg80211_rnr_iter_ret(9), cfg80211_iter_rnr(9), cfg80211_defragment_element(9), cfg80211_send_layer2_update(9) — RNR iteration + its return enum, element defragmentation, and the layer-2 update notification. 🧚

---

💖 Regulatory enforcement infrastructure

• Regulatory enforcement infrastructure(9), regulatory_hint(9), regulatory_set_wiphy_regd(9), regulatory_set_wiphy_regd_sync(9), wiphy_apply_custom_regulatory(9), freq_reg_info(9), reg_initiator_name(9), regulatory_pre_cac_allowed(9), Internal regulatory db functions(9), reg_query_regdb_wmm(9) — hints, per-wiphy regd (sync and async flavours), custom regulatory, freq reg info, initiator names, pre-CAC checks, and the internal regdb WMM query. Regulatory girlies, we see you 🌍
• cfg80211_scan_done(9), cfg80211_sched_scan_results(9), cfg80211_sched_scan_stopped(9), cfg80211_sched_scan_stopped_locked(9), cfg80211_inform_bss_frame_data(9), cfg80211_gen_new_bssid(9), cfg80211_is_element_inherited(9), cfg80211_merge_profile(9), enum cfg80211_bss_frame_type(9), cfg80211_get_ies_channel_number(9), cfg80211_ssid_eq(9), cfg80211_inform_bss_data(9), __cfg80211_get_bss(9), cfg80211_get_bss(9), cfg80211_ref_bss(9), cfg80211_put_bss(9), cfg80211_unlink_bss(9), cfg80211_bss_iter(9) — scan done, sched scan results/stopped (locked variant is a whole separate entry, don't merge them!), BSS informing, new BSSID gen, element inheritance, profile merging, BSS frame types, IEs channel number, SSID equality, and the get/ref/put/unlink/iter BSS crew. And yes — __cfg80211_get_bss(9) has two underscores, it's a different function from cfg80211_get_bss(9), copy them exactly 🙈
• cfg80211_rx_mlme_mgmt(9), cfg80211_auth_timeout(9), struct cfg80211_rx_assoc_resp_data(9), cfg80211_rx_assoc_resp(9), struct cfg80211_assoc_failure(9), cfg80211_assoc_failure(9), cfg80211_tx_mlme_mgmt(9), cfg80211_rx_unprot_mlme_mgmt(9), cfg80211_michael_mic_failure(9), cfg80211_ibss_joined(9), cfg80211_notify_new_peer_candidate(9) — MLME RX/TX, auth timeout, assoc response data + event, assoc failure struct + event, unprotected MLME RX, Michael MIC failure, IBSS joined, new peer candidate. 😭
• RFkill integration(9), wiphy_rfkill_set_hw_state_reason(9), wiphy_rfkill_start_polling(9), wiphy_rfkill_stop_polling(9) — set HW state with a reason, and start/stop the polling. ✈️

vendor commands & test mode

• Vendor commands(9), cfg80211_vendor_cmd_alloc_reply_skb(9), cfg80211_vendor_cmd_reply(9), cfg80211_vendor_cmd_get_sender(9), cfg80211_vendor_event_alloc(9), cfg80211_vendor_event_alloc_ucast(9), cfg80211_vendor_event(9) — allocate a reply skb, send the reply, get the sender, alloc events (incl. unicast), send the event 🎀
• Test mode(9), cfg80211_testmode_alloc_reply_skb(9), cfg80211_testmode_reply(9), cfg80211_testmode_alloc_event_skb(9), cfg80211_testmode_event(9) — same energy, test-mode edition. 🧪

connection events & notifications

• struct cfg80211_fils_resp_params(9), struct cfg80211_connect_resp_params(9), cfg80211_connect_done(9), cfg80211_connect_bss(9), cfg80211_connect_result(9), cfg80211_connect_timeout(9), struct cfg80211_roam_info(9), cfg80211_roamed(9), cfg80211_port_authorized(9), cfg80211_disconnected(9) — FILS resp params, connect resp params, done, connect_bss, connect_result, timeout, roam info + roamed, port authorized, disconnected. The whole connect-and-leave saga 💀
• cfg80211_ready_on_channel(9), cfg80211_remain_on_channel_expired(9), cfg80211_tx_mgmt_expired(9), cfg80211_sinfo_alloc_tid_stats(9), cfg80211_link_sinfo_alloc_tid_stats(9), cfg80211_sinfo_release_content(9), cfg80211_new_sta(9), cfg80211_del_sta_sinfo(9), cfg80211_del_sta(9), cfg80211_conn_failed(9) — ROC ready/expired, mgmt TX expired, TID stat allocation (station and per-link versions), sinfo content release, new/delete station (with and without sinfo), connection failed ⭐
• struct cfg80211_rx_info(9), cfg80211_rx_mgmt_ext(9), cfg80211_rx_mgmt_khz(9), cfg80211_rx_mgmt(9), struct cfg80211_tx_status(9), cfg80211_mgmt_tx_status_ext(9), cfg80211_mgmt_tx_status(9), cfg80211_control_port_tx_status(9), cfg80211_rx_control_port(9) — RX info struct, the three rx_mgmt flavours, tx status struct, mgmt tx status (ext and plain), control port tx status, rx control port 📡
• cfg80211_cqm_rssi_notify(9), cfg80211_cqm_pktloss_notify(9), cfg80211_cqm_txe_notify(9), cfg80211_cqm_beacon_loss_notify(9), __cfg80211_radar_event(9), cfg80211_sta_opmode_change_notify(9), cfg80211_cac_event(9), cfg80211_background_cac_abort(9), cfg80211_gtk_rekey_notify(9), cfg80211_pmksa_candidate_notify(9) — the CQM notification quartet (RSSI, packet loss, TXE, beacon loss), the radar event (double underscore again, bestie!), opmode change, CAC event, background CAC abort, GTK rekey notify, PMKSA candidate notify 🔔
• cfg80211_rx_spurious_frame(9), cfg80211_rx_unexpected_4addr_frame(9), cfg80211_probe_status(9), cfg80211_report_obss_beacon_khz(9), cfg80211_report_obss_beacon(9), struct cfg80211_beaconing_check_config(9),

…and here's the rest of the extended family, bestie — every single one of them, no skips, no "etc." cop-outs 💖

• cfg80211_reg_check_beaconing(9)
• cfg80211_reg_can_beacon(9)
• cfg80211_reg_can_beacon_relax(9)
• cfg80211_ch_switch_notify(9)
• cfg80211_ch_switch_started_notify(9)
• ieee80211_operating_class_to_band(9)
• ieee80211_operating_class_to_chandef(9)
• ieee80211_chandef_to_operating_class(9)
• ieee80211_chandef_to_khz(9)
• cfg80211_tdls_oper_request(9)
• cfg80211_calculate_bitrate(9)
• cfg80211_unregister_wdev(9)
• cfg80211_register_netdevice(9)
• cfg80211_unregister_netdevice(9)
• struct cfg80211_ft_event_params(9) — a whole ✨struct✨ in the list, she's not like the other girls
• cfg80211_ft_event(9)
• cfg80211_get_p2p_attr(9)
• ieee80211_ie_split_ric(9)
• ieee80211_ie_split(9)
• ieee80211_fragment_element(9)
• cfg80211_report_wowlan_wakeup(9)
• cfg80211_crit_proto_stopped(9)
• ieee80211_get_num_supported_channels(9)
• cfg80211_check_combinations(9)
• cfg80211_iter_combinations(9)
• cfg80211_get_radio_idx_by_chan(9)
• cfg80211_stop_link(9)
• cfg80211_stop_iface(9)
• cfg80211_shutdown_all_interfaces(9) — the final boss energy, honestly 😭
• wiphy_ext_feature_set(9)
• wiphy_ext_feature_isset(9)
• cfg80211_free_nan_func(9)
• struct cfg80211_nan_match_params(9) — another struct, we stan a structured queen 🎀
• cfg80211_nan_match(9)
• cfg80211_nan_func_terminated(9)
• cfg80211_nan_sched_update_done(9)
• cfg80211_external_auth_request(9)
• cfg80211_pmsr_report(9)
• cfg80211_pmsr_complete(9)
• cfg80211_iftype_allowed(9)
• cfg80211_assoc_comeback(9) — the comeback of all comebacks fr fr
• cfg80211_update_owe_info_event(9)
• cfg80211_bss_flush(9)
• cfg80211_bss_color_notify(9)
• cfg80211_obss_color_collision_notify(9)
• cfg80211_color_change_started_notify(9)
• cfg80211_color_change_aborted_notify(9)
• cfg80211_color_change_notify(9)
• cfg80211_6ghz_power_type(9)
• cfg80211_links_removed(9)
• struct cfg80211_mlo_reconf_done_data(9) — third struct of the list, she ate and left no crumbs 💅
• cfg80211_mlo_reconf_add_done(9)
• cfg80211_schedule_channels_check(9)
• cfg80211_epcs_changed(9)
• cfg80211_next_nan_dw_notif(9)
• cfg80211_nan_cluster_joined(9)
• cfg80211_nan_ulw_update(9)
• cfg80211_nan_channel_evac(9)
• wiphy_locked_debugfs_read(9)
• wiphy_locked_debugfs_write(9)
• cfg80211_s1g_get_start_freq_khz(9)
• cfg80211_s1g_get_end_freq_khz(9)
• cfg80211_s1g_get_primary_sibling(9)
• cfg80211_incumbent_signal_notify(9)

---

And that's a wrap on the whole page, bestie 🫶 You made it to the end — go read something fun now, like cfg80211_pmsr_report(9), she'd love the attention.

tiny housekeeping so nobody comes for me: this page lives in ./include/net, it's dated October 2026, and the page itself is struct cfg8...capabilities(9) — yes, the title is literally truncated in the header, iconic, no notes 💀✨

bye bestie, go forth and configure your kernel 🌈