ENUM IWL_TOF_RESPONSE_MODE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enum iwl_tof_response_mode(9) ✨

okay so bestie, we're in the Kernel API Manual, section 9, and today's main character is enum iwl_tof_response_mode β€” literally the enum that decides when your TOF measurements get reported back to you. it's giving "choose your delivery speed" energy πŸ’Œ


🌸 NAME 🌸

enum iwl_tof_response_mode β€” TOF response mode. that's it, that's the vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

enum iwl_tof_response_mode {
    IWL_MVM_TOF_RESPONSE_ASAP ,
    IWL_MVM_TOF_RESPONSE_TIMEOUT ,
    IWL_MVM_TOF_RESPONSE_COMPLETE

};

like, three constants, three whole personalities. pick your fighter πŸ’…


πŸ‘‘ Constants πŸ‘‘

  • IWL_MVM_TOF_RESPONSE_ASAP β€” report each AP measurement separately as soon as possible. no waiting, no batching, just instant delivery ✨ but heads up: (not supported for this release) β€” so don't get too attached, bestie 😭
  • IWL_MVM_TOF_RESPONSE_TIMEOUT β€” report all AP measurements as a batch upon timeout expiration. you wait, the timer runs out, and then boom β€” the whole batch arrives at once. orderly, patient, lowkey a vibe 🫢
  • IWL_MVM_TOF_RESPONSE_COMPLETE β€” report all AP measurements as a batch at the earlier of: measurements completion / timeout expiration. which one comes first, you ask? yes. whichever hits first, you get the batch. main character energy of "why not both, but sooner" πŸ”₯
ngl the whole enum is just three answers to "when do i get my data?" and honestly? relatable.

πŸ”— SEE ALSO πŸ”—

all of these live in the Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h, and there are so many of them, so buckle in bestie β€” we're doing the whole list, no skips, periodt πŸ’€

  • 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_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, that's the entire friend group and they all showed up to the party πŸŽ‰


and that's the page, bestie!! πŸ§šπŸ’œ this little icon dropped back in October 2026, straight from the source path ./drivers/net/wireless/intel/i... (yes it's literally truncated like that in the footer, don't come for me πŸ™ˆ), and it's filed under enum iwl_tof_response_mode(9) in the Kernel API Manual. slay, go read your TOF measurements responsibly βœ¨πŸŽ€

πŸ“¦ where this page comes from