STRUCT IWL_TOF_RANGE_RSP_NTFY_V5(9)

💅 struct iwl_t..._rsp_ntfy_v5 — Kernel API Manual, bestie ✨

okay so this is a page out of the Kernel API Manual, and the star of the show is struct iwl_t..._rsp_ntfy_v5 — the ranging response notification. it's giving "the Wi-Fi card texted back and here's the whole group chat" energy 🦋

---

🌸 NAME 🌸

struct iwl_tof_range_rsp_ntfy_v5 — ranging response notification. that's it, that's the whole vibe 🎀

---

✨ SYNOPSIS ✨

struct iwl_tof_range_rsp_ntfy_v5 {
    u8 request_id;
    u8 request_status;
    u8 last_in_batch;
    u8 num_of_aps;
    struct iwl_tof_range_rsp_ap_entry_ntfy_v3 ap[IWL_TOF_MAX_APS];
 };

look at her. four lil u8s and a whole array of per-AP lore. she's compact, she's iconic, she's literally the reply you've been waiting for 🫶

---

🧚 Members 🧚

• request_id — the Token ID of the corresponding Range request. it's the "replying to your message" tag fr fr — how you match the reply to the ask 💌
• request_status — the status of the current measurement session, and it's one of enum iwl_tof_response_status. vibe check for the whole session 🔥
• last_in_batch — the reprot policy (yes that's how it's spelled in the original, no i will not be fixing the source's typos 💀) — it kicks in when not all responses are uploaded at once ✨
• num_of_aps — number of APs to measure. error if > IWL_TOF_MAX_APS — she will simply not tolerate overcapacity, periodt 🙈
• ap — per-AP data. one struct iwl_tof_range_rsp_ap_entry_ntfy_v3 per AP, and honestly each one is a main character in its own right 👑

---

🌈 SEE ALSO 🌈

so many cross-references, bestie, buckle up. first up, the kernel file where she lives: ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h 📍

then the whole extended friend group:

• 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)
• enum iwl_responder_dyn_cfg_valid_flags(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_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. that's a whole party and every single one of them is invited 💜

---

and that's the page!! source path is ./drivers/net/wireless/intel/i..., dated October 2026, and the page signs off as struct iwl_t..._rsp_ntfy_v5(9) — mwah, no notes, go read the kernel source bestie 💅✨