ENUM IWL_RESPONDER_DYN_CFG_VALID_FLAGS(9)

💅 enum iwl_responder_dyn_cfg_valid_flags 💅

okay so bestie, welcome to the Kernel API Manual, section 9 — yes we're in the kernel docs and yes we're gonna have a good time. This one's about enum iwl_responder_dyn_cfg_valid_flags, and ngl its whole entire job is just... being the valid flags for dyn_config_cmd. That's it. That's the vibe. 🎀

---

✨ NAME ✨

enum iwl_responder_dyn_cfg_valid_flags — the valid flags for dyn_config_cmd, fr fr 🫶

---

🌈 SYNOPSIS 🌈

enum iwl_responder_dyn_cfg_valid_flags {
    IWL_RESPONDER_DYN_CFG_VALID_LCI ,
    IWL_RESPONDER_DYN_CFG_VALID_CIVIC ,
    IWL_RESPONDER_DYN_CFG_VALID_PASN_STA

};

like, that's the whole squad right there 👑

---

🦋 Constants 🦋

okay so these are the three members and each one is iconic in its own way:

• IWL_RESPONDER_DYN_CFG_VALID_LCI — the LCI data is valid. slay, it checked out ✨
• IWL_RESPONDER_DYN_CFG_VALID_CIVIC — the Civic data is valid. periodt 💅
• IWL_RESPONDER_DYN_CFG_VALID_PASN_STA — the pasn_addr, HLTK and cipher fields are valid. the way this one is lowkey doing the most — three fields at once, main character energy 👑

---

🌸 SEE ALSO 🌸

first up, the lore lives in the kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h — go read it, iykyk 💜

and then the extended family, because this struct literally cannot be normal about cross-references. every single one of these besties, no cap:

• enum iwl_location_subcmd_ids(9)
• enum iwl_location_frame_format(9)
• enum iwl_location_bw(9)
• enum iwl_location_format_bw(9)
• struct iwl_tof_config_cmd(9)
• enum iwl_tof_bandwidth(9)
• enum iwl_tof_responder_cmd_valid_field(9)
• enum iwl_tof_responder_cfg_flags(9)
• struct iwl_tof_responder_config_cmd_v6(9)
• struct iwl_tof_responder_config_cmd_v7(9)
• struct iwl_tof_responder_config_cmd_v8(9)
• struct iwl_tof_responder_config_cmd_v9(9)
• struct iwl_tof_responder_config_cmd(9)
• struct iwl_tof_responder_dyn_config_cmd_v2(9)
• struct iwl_tof_responder_dyn_config_cmd(9)
• struct iwl_tof_range_req_ext_cmd(9)
• enum iwl_tof_location_query(9)
• enum iwl_initiator_ap_flags(9)
• struct iwl_tof_range_req_ap_entry_v3(9)
• struct iwl_tof_range_req_ap_entry_v4(9)
• enum iwl_location_cipher(9)
• struct iwl_tof_range_req_ap_entry_v6(9)
• struct iwl_tof_range_req_ap_entry_v7(9)
• struct iwl_tof_range_req_ap_entry_v8(9)
• struct iwl_tof_range_req_ap_entry_v9(9)
• struct iwl_tof_range_req_ap_entry(9)
• enum iwl_tof_response_mode(9)
• enum iwl_tof_initiator_flags(9)
• struct iwl_tof_range_req_cmd_v5(9)
• struct iwl_tof_range_req_cmd_v7(9)
• struct iwl_tof_range_req_cmd_v8(9)
• struct iwl_tof_range_req_cmd_v9(9)
• struct iwl_tof_range_req_cmd_v11(9)
• struct iwl_tof_range_req_cmd_v12(9)
• struct iwl_tof_range_req_cmd_v13(9)
• struct iwl_tof_range_req_cmd(9)
• enum iwl_tof_entry_status(9)
• struct iwl_tof_range_rsp_ap_entry_ntfy_v3(9)
• struct iwl_tof_range_rsp_ap_entry_ntfy_v4(9)
• struct iwl_tof_range_rsp_ap_entry_ntfy_v5(9)
• struct iwl_tof_range_rsp_ap_entry_ntfy_v7(9)
• struct iwl_tof_range_rsp_ap_entry_ntfy(9)
• enum iwl_tof_response_status(9)
• struct iwl_tof_range_rsp_ntfy_v5(9)
• struct iwl_tof_range_rsp_ntfy_v6(9)
• struct iwl_tof_range_rsp_ntfy_v7(9)
• struct iwl_tof_range_rsp_ntfy_v9(9)
• struct iwl_tof_range_rsp_ntfy(9)
• struct iwl_tof_mcsi_notif(9)
• struct iwl_tof_range_abort_cmd(9)
• struct iwl_ftm_responder_stats(9)

like... 51 of them. not me counting. okay i counted. ate and left no crumbs 🍓

---

bestie real talk: every single one of those references matters, don't skip them just because the list is long 😭

---

mwah, that's the page!! source ./drivers/net/wireless/intel/i..., dated October 2026, and it's all about enum iwl_res..._valid_flags(9) obviously 💖 stay hydrated, go read your kernel headers, ily 🧚‍♀️⭐💜