iwl_mvm_te_scheduled(9)

💖 iwl_mvm_te_scheduled(9) 💖

okay so bestie, welcome to the Kernel API Manual — today's main character is iwl_mvm_te_scheduled, a little function that simply checks if the firmware actually received the TE cmd. that's it. that's the vibe check. ✨

---

🌸 NAME 🌸

iwl_mvm_te_scheduled — check if the fw received the TE cmd 👀

like, literally just a check. no cap.

---

🦋 SYNOPSIS 🦋

bool iwl_mvm_te_scheduled (struct iwl_mvm_time_event_data *te_data );

one function, one argument, returns a bool. icon behavior honestly. 💅

---

🎀 ARGUMENTS 🎀

• te_data — the time event data that corresponds to that time event. it's giving "the paperwork for the thing," bestie. you hand it over, it tells you what's up. 🫶

---

⭐ RETURN ⭐

• true if this TE is added to the fw 🔥
• false otherwise 😭

that's the whole return story. no plot twist.

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/net/wireless/intel/iwlwifi/mvm/time-event.h
• Time Events - what is it?(9)
• Abstraction to the driver(9)
• iwl_mvm_protect_session(9)
• iwl_mvm_stop_session_protection(9)
• iwl_mvm_rx_roc_notif(9)
• iwl_mvm_start_p2p_roc(9)
• iwl_mvm_stop_roc(9)
• iwl_mvm_remove_time_event(9)
• iwl_mvm_te_clear_data(9)
• iwl_mvm_schedule_csa_period(9)
• iwl_mvm_schedule_session_protection(9)
• iwl_mvm_rx_session_protect_notif(9)

the whole friend group fr fr. go read the gang, iykyk. 📚✨

---

go off, check your time events, and remember: if te_data doesn't line up, that's a you problem, not a firmware problem. 💀

---

sign-off szn: source/version is ./drivers/net/wireless/intel/i... and the date on this one is October 2026 — so yeah, she's from the future, she's iconic, she's iwl_mvm_te_scheduled(9). periodt. 👑🎀💜