ENUM IWL_TOF_RESPONSE_STATUS(9)
π NAME π
Okay bestie, welcome to the Kernel API Manual entry for enum iwl_tof_response_status β aka the tof response status enum. Itβs giving βdid the range measurement succeed or notβ energy, and weβre about to get into it β¨π
.
π‘ SYNOPSIS π‘
enum iwl_tof_response_status {
IWL_TOF_RESPONSE_SUCCESS ,
IWL_TOF_RESPONSE_TIMEOUT ,
IWL_TOF_RESPONSE_ABORTED ,
IWL_TOF_RESPONSE_FAILED
};
π Constants π
These are the constants, and each one has a whole personality, no cap:
IWL_TOF_RESPONSE_SUCCESSβ successful range. Periodt, we love a win π―β¨IWL_TOF_RESPONSE_TIMEOUTβ request aborted due to timeout expiration. partial result of ranges done so far is included in the response. So yeah, it timed out, but it still brought receipts for the ranges it finished ππ«ΆIWL_TOF_RESPONSE_ABORTEDβ Measurement aborted by command. Somebody hit the abort button, iconic behavior πIWL_TOF_RESPONSE_FAILEDβ Measurement request command failed. Not slay, honestly, itβs a fail π
π SEE ALSO π
The kernel file is ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h β thatβs home base π β and hereβs the whole SEE ALSO friend group, every single ref in the original order:
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)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)
Alright bestie, thatβs the whole page π Source/version vibe: ./drivers/net/wireless/intel/i..., dated October 2026. Go forth and range responsibly, mwah πβ¨π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms