STRUCT CFG80211_TID_CONFIG(9)

📦 version 7.3.1, in nixpkgs unstable

💖 struct cfg80211_tid_config — TID configuration 💖

Kernel API Manual, section 9, bestie ✨ keep that in your notes.

💖 NAME 💖

struct cfg80211_tid_config — TID configuration. That's the whole name vibe: this struct is literally the TID configuration main character, no cap 💅

✨ SYNOPSIS ✨

okay so here's the exact shape, copy it character for character:

struct cfg80211_tid_config {
    const u8 *peer;
    u32 n_tid_conf;
    struct cfg80211_tid_cfg tid_conf[];
};

🌸 Members 🌸

  • peer — Station's MAC address. That's the station's MAC, periodt 🫶
  • n_tid_conf — Number of TID specific configurations to be applied. Count 'em, bestie 🔥
  • tid_conf — Configuration change info. It's giving "here's what's changing" ✨

✨ SEE ALSO ✨

okay bestie, this is the part where the page just vibes at you with the entire cfg80211 cinematic universe 😭 like, every single cross-reference the kernel docs could think of, all in one place. none of it is fluff tho — these are the real siblings, cousins and distant cousins of struct cfg80211_tid_config(9), and you can just pull up any of them with man 9 <name>. let's walk it 💅

First up, the home base itself — like, obvi — is the kernel header ./include/net/cfg80211.h. Everything below lives in or around that file's world 🎀

🦋 Actions and configuration 🦋

this chunk is the main character energy section — channels, AP settings, stations, SAR, mesh, the whole situation. ngl it's a lot, but it's all right there, no cap 🔥

🌸 Scanning and BSS list handling 🌸

scanning era!! this is where you go looking for networks and then keep a whole little list of them 🫶

  • 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)
  • 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)
  • 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)

🧚 Neighbor Awareness Networking (NAN) 🧚

yes bestie, NAN gets its own little clique. proximity networking said "i'm the moment" 💅

  • 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)

💜 the rest of the cfg80211 crew 💜

PMK, external auth, FTM, PMSR, management frames, and then the big one: struct cfg80211_ops(9) — the function table where drivers strut their stuff. also all the wiphy flags and capas, iykyk ✨

  • 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)
  • 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 cfg80211_pmsr_capabilities(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)

👑 wiphy lifecycle & locking, aka the whole glow-up arc 👑

private data, registration, locking, and not one, not two, but a whole squad of work-queue helpers. this is the struct wiphy's personal assistant team fr fr 🎀

🌈 Utility functions 🌈

the little helpers that ate 💅 channel/frequency conversions, header lengths, mesh header length — the stuff you reach for like, constantly.

🍓 Data path helpers 🍓

frame conversion, A-MSDU checks, and the find-the-element squad (yes there's a _match version, an ext version, and a vendor version — it's giving "collect them all" 🦋) plus RNR iteration and Layer 2 update sending.

⭐ Regulatory enforcement infrastructure ⭐

the vibe-check police for radio rules 🌍 regulatory hints, custom regd, freq info, and the pre-CAC question. yes, "Internal regulatory db functions" is its own mini-section — it said "i'm internal, don't @ me" 🙈

💀 scan / BSS notifications and the MLME crowd 💀

scan done, sched scan results, "stopped" and "stopped_locked" (yes bestie, the _locked variant is a whole separate manpage and you WILL respect it), BSS get/put/ref/unlink, and then all the MLME mgmt callbacks: auth timeout, assoc resp, deauth-ish stuff, michael mic failure, ibss joined, new peer candidate 👑

🎀 RFkill integration 🎀

three helpers, all business: set hw state (with a reason), start polling, stop polling.

🫶 Vendor commands 🫶

alloc a reply skb, send the reply, get the sender, plus the event alloc/reply trio.

🧚 Test mode 🧚

literally four functions and they're all about reply/event skbs. iconic, no notes.

🔥 connect / roam / station / mgmt notifications 🔥

this is the big notification era — connect done, roamed, disconnected, remain-on-channel expiry, station added/deleted, mgmt tx status, control port, CQM notifications, radar, CAC, GTK rekey, PMKSA candidates, probe status, and OBSS beacon reporting. it's giving "every event your driver ever wanted to tell userspace" 💜

and that's the whole reference wall, bestie — not a single one skipped, fr fr 💖 (and yes, the original literally ends that list on a dangling comma. we love a chaotic queen 🙈)

okay bestie, the cross-reference list does not stop, she's still going, and honestly? iconic of her. here's the rest of the crew, in the exact order the page hands them to you — no notes attached, just names and numbers, so go read them if you're nosy 🎀

and that's a wrap on the whole page, bestie 💜 sixty-four links later and we made it out alive, which is honestly a slay.

tiny housekeeping moment — this page lives in ./include/net, it's dated October 2026, and its title is struct cfg80211_tid_config(9). that's the source, the date, and the name, all accounted for, no cap 🫶

go forth and configure your TIDs, you absolute main character ✨🌸

📦 where this page comes from