STRUCT IEEE80211_UHR_DPS_INFO(9)

💅 struct ieee80211_uhr_dps_info — DPS operation information 🎀

So bestie, we're deep in the ieee80211-uhr.h lore today and this one is literally the little struct that could. It's struct ieee80211_uhr_dps_info from the Kernel API Manual, and it's giving "one field, infinite responsibilities" energy. Iconic, honestly.

---

✨ SYNOPSIS ✨

struct ieee80211_uhr_dps_info {
    __le32 params;
};

Yes, that's it. One __le32. Don't let the tiny synopsis fool you — that one field is packed with SO much meaning, iykyk.

---

🫶 Members 🫶

• params — okay so this is the whole DPS operation parameter packed into a single __le32, and it's lowkey carrying the entire personality. It's the home of all of these sub-fields, so buckle up:
  • DPS Padding Delay — the minimum MAC padding duration that a DPS STA in an ICF needs in order to actually cause the STA to transition from the lower capability mode to the higher capability mode. Units? 4 µs, bestie. Write that down. ⏱️
  • DPS Transition Delay — the amount of time a DPS STA needs to transition from the higher capability mode back down to the lower capability mode. Also in units of 4 µs. The way it goes down but also needs time to go down... relatable. 😭
  • ICF Required — tells you when the DPS assisting STA has to transmit an ICF frame to the peer DPS STA before doing the frame exchanges with that peer DPS STA in a TXOP. The values:
    • 1 → transmission of the ICF frame to the peer DPS STA prior to any frame exchange is needed. Yes ma'am. 🔥
    • 0 → ICF transmission before the frame exchanges with the peer DPS STA is only needed if the frame exchange is performed in the HC mode.
  • Parameterized Flag — the main character of mode selection, fr fr:
    • 0 → only 20 MHz, 1 SS, non-HT PPDU format with the data rate of 6, 12, and 24 Mb/s as the default mode are supported by the DPS STA in the LC mode.
    • 1 → a bandwidth up to the bandwidth indicated in the LC Mode Bandwidth field, a number of spatial streams up to the NSS indicated in the LC Mode Nss field, and an MCS up to the MCS indicated in the LC Mode MCS fields are supported by the DPS STA in the LC mode as the parameterized mode. Cute and parameterized 💅
  • LC Mode Bandwidth — the maximum bandwidth supported by the STA in the LC mode. That's the ceiling, no cap (well, literally a cap). 🌈
  • LC Mode NSS — the maximum number of spatial streams supported by the STA in the LC mode.
  • LC Mode MCS — the highest MCS supported by the STA in the LC mode. Highest! Not average! 👑
  • Mobile AP DPS Static HCM —
    • 1 → indicates that it will remain in the DPS high capability mode until the next TBTT on that link.
    • 0 → otherwise. (The humble "otherwise." we love her 🍓)

---

💖 Description 💖

This structure is the "DPS Operation Parameter field" of "UHR Operation Element" fields, exactly as described in P802.11bn_D1.3 subclause 9.4.1.87. Also, go look at Figure 9-207u — it's all laid out there, no cap. 🦋

Refer to IEEE80211_UHR_DPS* for the whole family of related stuff.

---

🔍 SEE ALSO 🔍

Kernel file ./include/linux/ieee80211-uhr.h struct ieee80211_uhr_npca_info(9), enum ieee80211_uhr_dbe_oper_bw(9), ieee80211_uhr_dbe_bw_mhz(9), struct ieee80211_uhr_dbe_info(9), struct ieee80211_uhr_p_edca_info(9), enum ieee80211_uhr_dbe_max_supported_bw(9), ieee80211_uhr_capa_get_om_pu_to_us(9)

---

Okay but real talk: this struct lives in ./include/linux and the page is dated October 2026, so if you're reading this from a future where all of this is old news — slay, tell us how the DPS saga ends 💀

Later bestie!! Stay parameterized, stay in your highest capability mode, and remember: one __le32 can hold multitudes. 💜✨🎀

— signed off from ./include/linux, October 2026, struct ieee...uhr_dps_info(9) 🧚‍♀️