ieee80211_e..._delay_in_us(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ieee80211_emlsr_pad_delay_in_us(9) β€” the Kernel API Manual glow-up ✨

okay so bestie, welcome to the Kernel API Manual πŸŽ€ and today's main character is ieee80211_emlsr_pad_delay_in_us(9) β€” yes the whole title, the one that got elided in the header because it's long and the manpage gods ran out of column space 😭. Anyway. She's a tiny little helper function, she's iconic, and she has exactly one job. Let's get into it πŸ¦‹


✨ NAME ✨

ieee80211_emlsr_pad_delay_in_us β€” Fetch the EMLSR Padding delay in microseconds πŸ’«

that's it. that's the whole vibe. she fetches. she converts. she slays. no cap πŸ”₯


🌸 SYNOPSIS 🌸

u32 ieee80211_emlsr_pad_delay_in_us (u16 eml_cap);

look at her go 😭 tiny signature, big energy. you hand her a u16 and she hands you back a u32 β€” glow-up in a single call fr fr πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • eml_cap β€” the EML capabilities field value, pulled straight out of the common info field of the Multi-link element πŸ’– like, this is the raw field value you're feeding her, so make sure it's actually the right one and not some random number you found in a packet capture πŸ™ˆ iykyk.

⭐ RETURN ⭐

she returns the EMLSR Padding delay (in microseconds, bestie β€” microseconds, not milli, not nano, don't come for me πŸ’€) as encoded in the EML Capabilities field.

so the number's already living in that capability field, and she's just... getting it out and handing it to you. the way that she's literally just a decoder πŸŽ€ no extra math, no surprises, no side quests.


πŸ’œ SEE ALSO πŸ’œ

okay this part is a LOT, she has a huge friend group, so buckle up 🍼. the whole squad lives in the kernel file ./include/linux/ieee80211-eht.h:

like... that's the whole group chat right there 😭 and notice her siblings ieee80211_emlsr_trans_delay_in_us(9), ieee80211_emlmr_pad_delay_in_us(9), ieee80211_emlmr_trans_delay_in_us(9) and ieee80211_eml_trans_timeout_in_us(9) are all in there too β€” family reunion fr fr πŸ’…. also peep the struct prefix before a bunch of them, that's load-bearing, don't drop it 🫢.


πŸ’‘ friendly reminder bestie: the eml_cap you feed her is supposed to be the EML capabilities field value from the common info field of the Multi-link element. don't be out here passing vibes πŸ’€

and that's the page!! 🌈 brought to you from ./include/linux, dated October 2026, and signed off by your girl ieee80211_e..._delay_in_us(9) herself (still abbreviated in the footer because the terminal is a hater 😭). stay hydrated, read your multi-link elements, and happy padding-delay fetching bestie πŸ“πŸ’–βœ¨

πŸ“¦ where this page comes from