STRUCT IWL_TOF_RANGE_RSP_NTFY_V9(9)

💅 struct iwl_tof_range_rsp_ntfy_v9 — ranging response notification ✨

okay so this is a page straight out of the Kernel API Manual bestie, and it's all about struct iwl_tof_range_rsp_ntfy_v9. she's the ranging response notification struct and honestly? she ate. let's get into it 💖

---

🌸 NAME 🌸

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

---

✨ SYNOPSIS ✨

struct iwl_tof_range_rsp_ntfy_v9 {
    u8 request_id;
    u8 num_of_aps;
    u8 last_report;
    u8 reserved;
    struct iwl_tof_range_rsp_ap_entry_ntfy_v7 ap[IWL_TOF_MAX_APS];
 };

look at her. four little u8s and then the main-character array ap holding IWL_TOF_MAX_APS entries of struct iwl_tof_range_rsp_ap_entry_ntfy_v7. iconic lineup ngl 👑

---

🦋 Members 🦋

• request_id — the Token ID of the matching Range request. it's giving "which conversation is this" energy, iykyk 🫶
• num_of_aps — how many APs results you got. the headcount, fr fr.
• last_report — 1 if no more FTM sessions are scheduled, 0 otherwise. so like… 1 means that's a wrap, 0 means we're still going 💀
• reserved — reserved. literally just reserved. she's sitting there being reserved and we respect her privacy 🙈
• ap — per-AP data. all the AP lore lives here ✨

---

💜 SEE ALSO 💜

okay this is the part where the whole group chat gets tagged, and no i'm not leaving anyone out:

• the Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h
• 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_v5(9)
• struct iwl_tof_range_rsp_ntfy_v6(9)
• struct iwl_tof_range_rsp_ntfy_v7(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 i said. the whole extended family. every single one of them made it to the function 💅

---

no cap, everything above is exactly what the page says — same members, same 0 and 1, same array type, same big SEE ALSO guest list. i didn't invent a single crumb 🍓

so that's her!! go forth and range responsibly bestie 🌈⭐

source: ./drivers/net/wireless/intel/i... — dated October 2026 — and yes the footer still calls her struct iwl_t..._rsp_ntfy_v9(9) because the terminal is a little dramatic about long names 😭 mwah, bye!! 🧚💖