STRUCT CFG80211_TTLM_PARAMS(9)

📦 version 7.3.1, in nixpkgs unstable

💖 struct cfg80211_ttlm_params(9) — Kernel API Manual 💖

okay so bestie, buckle up, because we're diving into struct cfg80211_ttlm_params and honestly? it's giving "small struct, big responsibilities." this is the Kernel API Manual page for it, and yes, we're doing the whole thing, no skipping, no cap. ✨

🌸 NAME 🌸

struct cfg80211_ttlm_params — the TID to link mapping parameters. that's it, that's the name, and it ate. 💅

🦋 SYNOPSIS 🦋

here's the literal shape of it, bestie — look at it, it's so tidy:

struct cfg80211_ttlm_params {
    u16 dlink[8];
    u16 ulink[8];
 };

two little arrays of u16, eight slots each, one for down and one for up. iconic symmetry, honestly. 🎀

👑 Members 👑

  • dlink — this one's your Downlink TID to link mapping, and it's defined in section 9.4.2.314 (TID-To-Link Mapping element) in Draft P802.11be_D4.0. so like, if you're wondering where the rules live, they live there. iykyk. 📜
  • ulink — same energy but for the Uplink TID to link mapping, and it's also as defined in section 9.4.2.314 (TID-To-Link Mapping element) in Draft P802.11be_D4.0. yes, the exact same section, bestie — they're matching. 🫶
lowkey a vibe check: both members point you at the same spec section, 9.4.2.314, inside Draft P802.11be_D4.0. don't go looking anywhere else, fr fr.

⭐ Description ⭐

so what's this struct even for? it's used for setting a TID to link mapping. that's the whole job. main character energy for a very specific task, and honestly? we respect it. 🔥

and that's the rundown so far — but hold up, there's more coming, so don't go anywhere 💜

👀 SEE ALSO 👀

okay bestie, this is the SEE ALSO section and it is literally the entire cfg80211 extended universe pulling up to the group chat at once 😭💖 every single reference is here, no skips, no cap. the source file itself is first, then the whole fam:

Right, bestie, so here's the rest of the cross-reference pile — this is the part of the page that's literally just vibes and links, so let's give it the respect it deserves. ✨

The regulatory / beaconing girlies — the ones who decide if you're even allowed to be transmitting:

Channel-switch announcements, because everyone deserves a heads-up before the channel moves:

Operating class + chandef conversions, aka the translator besties:

Random-but-iconic utility crew:

Interface + netdevice lifecycle, the "who's registering what now" section:

Fast transition, because roaming should be a glow-up not a whole ordeal:

P2P attribute hunting:

Information-element splitting and fragmenting, the arts-and-crafts table:

Wakeup + critical protocol drop-outs:

Channel bookkeeping, combos and radio lookups — very "let me check my calendar" energy:

Shutting things down, gracefully or otherwise (drama, but the necessary kind):

Extended feature flags, set it and check it:

NAN everything — the whole cluster, no notes:

Auth, PMSR and OWE event reporting:

Type checking and BSS housekeeping:

Colour / BSS colour notifications — the aesthetic corner of the kernel 🌈:

6 GHz power types and link removal:

MLO reconfiguration, because multi-link is a whole lifestyle:

Channel checks and EPCS:

More NAN, because there was somehow still more NAN:

Debugfs, locked and loaded:

S1G frequency math and primary sibling hunting:

And the final boss of the reference list:

And that's the page, bestie — you made it to the end 🫶 That was a lot of cross-references and you read every single one, which is genuinely iconic of you. No cap.

Little sign-off moment: this one lives in ./include/net, it's dated October 2026, and it's from the struct cfg80211_ttlm_params(9) Kernel API Manual. Go drink some water and go touch (a) grass — or at least a nl80211 socket. 💖🎀
📦 where this page comes from