ENUM IWL_TIME_EVENT_POLICY(9)

💫 enum iwl_time_event_policy(9) 💫

okay bestie so this is a page from the Kernel API Manual, section 9, and it's literally all about enum iwl_time_event_policy — the time event policy values. buckle up, it's giving "tiny enum, big feelings" 🎀

---

✨ NAME ✨

enum iwl_time_event_policy — time event policy values, periodt.

so here's the vibe check on notifications: a notification (both event and fragment, iykyk) includes a status that tells you whether the FW was able to schedule the event or not. for fragment start/end notifications the status is always success — no notes, always slay. and heads up: there is no start/end fragment notification for monolithic events. none. zero. don't go looking 👀

---

🌸 SYNOPSIS 🌸

enum iwl_time_event_policy {
    TE_V2_DEFAULT_POLICY ,
    TE_V2_NOTIF_HOST_EVENT_START ,
    TE_V2_NOTIF_HOST_EVENT_END ,
    TE_V2_NOTIF_INTERNAL_EVENT_START ,
    TE_V2_NOTIF_INTERNAL_EVENT_END ,
    TE_V2_NOTIF_HOST_FRAG_START ,
    TE_V2_NOTIF_HOST_FRAG_END ,
    TE_V2_NOTIF_INTERNAL_FRAG_START ,
    TE_V2_NOTIF_INTERNAL_FRAG_END ,
    TE_V2_START_IMMEDIATELY ,
    TE_V2_DEP_OTHER ,
    TE_V2_DEP_TSF ,
    TE_V2_EVENT_SOCIOPATHIC ,
    TE_V2_ABSENCE

};

---

🦋 CONSTANTS 🦋

okay here's the whole cast, main character energy only:

• TE_V2_DEFAULT_POLICY — independent, social, present, unoticable (yes that's literally how it's spelled in the source, we respect the typo 💅)
• TE_V2_NOTIF_HOST_EVENT_START — request/receive notification on event start
• TE_V2_NOTIF_HOST_EVENT_END — request/receive notification on event end
• TE_V2_NOTIF_INTERNAL_EVENT_START — internal FW use
• TE_V2_NOTIF_INTERNAL_EVENT_END — internal FW use.
• TE_V2_NOTIF_HOST_FRAG_START — request/receive notification on frag start
• TE_V2_NOTIF_HOST_FRAG_END — request/receive notification on frag end
• TE_V2_NOTIF_INTERNAL_FRAG_START — internal FW use.
• TE_V2_NOTIF_INTERNAL_FRAG_END — internal FW use.
• TE_V2_START_IMMEDIATELY — start time event immediately, no waiting around, no "let me think about it" 🏃‍♀️
• TE_V2_DEP_OTHER — depends on another time event
• TE_V2_DEP_TSF — depends on a specific time
• TE_V2_EVENT_SOCIOPATHIC — can't co-exist with other events of tha same MAC (again, the source's spelling, not mine — iconic honestly 💀)
• TE_V2_ABSENCE — are we present or absent during the Time Event.

💜 quick reminder that those internal FW use ones are, well, internal FW use — not your business, bestie, and that's fine.

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/time-event.h
• struct iwl_time_event_cmd(9)
• struct iwl_time_event_resp(9)
• struct iwl_time_event_notif(9)
• enum iwl_session_prot_conf_id(9)
• struct iwl_session_prot_cmd(9)
• struct iwl_session_prot_notif(9)

go read the whole friend group, they're all linked and they all ate 🫶

---

🎀 sign-off 🎀

and that's the page!! source/version situation is ./drivers/net/wireless/intel/i... and it's dated October 2026, all wrapped up under the header enum iwl_time_event_policy(9). you understood it, you slayed it, no cap. bye bestie 💖🌈✨