ENUM IWL_SESSION_PROT_CONF_ID(9)

💖 enum iwl_session_prot_conf_id — session protection's configurations 💖

okay bestie so real talk: this is a page straight out of the Kernel API Manual, and it's all about enum iwl_session_prot_conf_id — literally just the lil menu of configurations for session protection. that's it. that's the whole vibe. ✨

✨ SYNOPSIS ✨

enum iwl_session_prot_conf_id {
    SESSION_PROTECT_CONF_ASSOC ,
    SESSION_PROTECT_CONF_GO_CLIENT_ASSOC ,
    SESSION_PROTECT_CONF_P2P_DEVICE_DISCOV ,
    SESSION_PROTECT_CONF_P2P_GO_NEGOTIATION ,
    SESSION_PROTECT_CONF_MAX_ID

};

🌸 Constants 🌸

• SESSION_PROTECT_CONF_ASSOC — this one kicks off a session protection for association, and the firmware responds by allocating two events for you. valid for BSS_STA and P2P_STA. here's the whole situation:
  • 🎀 first up, a rather short event that can't be fragmented and rocks a very high priority. if every goes well (99% of the cases) the association should complete within this first event. during that event, no other activity will happen in the firmware — which is exactly why it can't be too long. the length of this event is hard-coded in the firmware: 300TUs.
  • 🦋 then there's another event which can be much longer (it's duration is configurable by the driver) — it has a slightly lower priority and it can be fragmented, which lets other activities run while this event is running. the firmware will automatically remove both events once the driver sets the BSS MAC as associated. heads up tho: neither of the events will be removed for the P2P_STA MAC. only the duration is configurable for this protection. 👑
• SESSION_PROTECT_CONF_GO_CLIENT_ASSOC — not used 💀 (literally nothing happens, it's giving placeholder energy)
• SESSION_PROTECT_CONF_P2P_DEVICE_DISCOV — schedules the P2P Device to be in listen mode. will be fragmented. valid only on the P2P Device MAC. (yep, valid only on the P2P Device MAC — it said it twice so we're saying it twice 🫶) the firmware will take into account the duration, the interval and the repetition count. no cap.
• SESSION_PROTECT_CONF_P2P_GO_NEGOTIATION — schedules the P2P Device to be able to run the GO Negotiation. will not be fragmented and not repetitive. valid only on the P2P Device MAC. only the duration will be taken into account. iconic, minimal, focused. 💅
• SESSION_PROTECT_CONF_MAX_ID — not used 🙈 (same story, it's just sitting there)

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/time-event.h

and these absolute main characters:

• enum iwl_time_event_policy(9)
• struct iwl_time_event_cmd(9)
• struct iwl_time_event_resp(9)
• struct iwl_time_event_notif(9)
• struct iwl_session_prot_cmd(9)
• struct iwl_session_prot_notif(9)

lowkey a warning for you: SESSION_PROTECT_CONF_GO_CLIENT_ASSOC and SESSION_PROTECT_CONF_MAX_ID are both marked not used — so don't go building your whole personality around them, bestie. 🍓

k that's the whole page!! mwah 💖 this came out of the kernel docs at ./drivers/net/wireless/intel/i..., dated October 2026, for enum iwl_se...prot_conf_id(9) — go forth and associate responsibly, ily, bye 🧚⭐