ENUM IWL_TOF_ENTRY_STATUS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ enum iwl_tof_entry_status(9) β€” Kernel API Manual πŸŽ€

✨ NAME ✨

enum iwl_tof_entry_status β€” TOF entry status. That’s the vibe, bestie: this is the Kernel API Manual page for the enum that tells you how a TOF entry went πŸ’…βœ¨

🌸 SYNOPSIS 🌸

Okay so here’s the exact enum shape, no cap:

       enum iwl_tof_entry_status {
           IWL_TOF_ENTRY_SUCCESS ,
           IWL_TOF_ENTRY_GENERAL_FAILURE ,
           IWL_TOF_ENTRY_NO_RESPONSE ,
           IWL_TOF_ENTRY_REQUEST_REJECTED ,
           IWL_TOF_ENTRY_NOT_SCHEDULED ,
           IWL_TOF_ENTRY_TIMING_MEASURE_TIMEOUT ,
           IWL_TOF_ENTRY_TARGET_DIFF_CH_CANNOT_CHANGE ,
           IWL_TOF_ENTRY_RANGE_NOT_SUPPORTED ,
           IWL_TOF_ENTRY_REQUEST_ABORT_UNKNOWN_REASON ,
           IWL_TOF_ENTRY_LOCATION_INVALID_T1_T4_TIME_STAMP ,
           IWL_TOF_ENTRY_11MC_PROTOCOL_FAILURE ,
           IWL_TOF_ENTRY_REQUEST_CANNOT_SCHED ,
           IWL_TOF_ENTRY_RESPONDER_CANNOT_COLABORATE ,
           IWL_TOF_ENTRY_BAD_REQUEST_ARGS ,
           IWL_TOF_ENTRY_WIFI_NOT_ENABLED ,
           IWL_TOF_ENTRY_RESPONDER_OVERRIDE_PARAMS

       };

πŸ’– Constants πŸ’–

These are the status constants, and every single one is getting a seat at the table 🫢:

  • IWL_TOF_ENTRY_SUCCESS β€” successful measurement. slay, it worked ✨
  • IWL_TOF_ENTRY_GENERAL_FAILURE β€” General failure. oof πŸ’€
  • IWL_TOF_ENTRY_NO_RESPONSE β€” Responder didn’t reply to the request. left on read 😭
  • IWL_TOF_ENTRY_REQUEST_REJECTED β€” Responder rejected the request. not the vibe πŸ™ˆ
  • IWL_TOF_ENTRY_NOT_SCHEDULED β€” Time event was scheduled but not called yet. ⏳
  • IWL_TOF_ENTRY_TIMING_MEASURE_TIMEOUT β€” Time event triggered but no measurement was completed. clock said nope ⭐
  • IWL_TOF_ENTRY_TARGET_DIFF_CH_CANNOT_CHANGE β€” No range due inability to switch from the primary channel. channel said no πŸ’…
  • IWL_TOF_ENTRY_RANGE_NOT_SUPPORTED β€” Device doesn’t support FTM. rip πŸ¦‹
  • IWL_TOF_ENTRY_REQUEST_ABORT_UNKNOWN_REASON β€” Request aborted due to unknown reason. mystery behavior πŸ‘‘
  • IWL_TOF_ENTRY_LOCATION_INVALID_T1_T4_TIME_STAMP β€” Failure due to invalid T1/T4. timestamp drama πŸŽ€
  • IWL_TOF_ENTRY_11MC_PROTOCOL_FAILURE β€” Failure due to invalid FTM frame structure. frame structure said absolutely not πŸ’€
  • IWL_TOF_ENTRY_REQUEST_CANNOT_SCHED β€” Request cannot be scheduled. calendar full energy 😭
  • IWL_TOF_ENTRY_RESPONDER_CANNOT_COLABORATE β€” Responder cannot serve the initiator for some period, period supplied in refusal_period. busy era 🫢
  • IWL_TOF_ENTRY_BAD_REQUEST_ARGS β€” Bad request arguments. args said nope πŸ™ˆ
  • IWL_TOF_ENTRY_WIFI_NOT_ENABLED β€” Wifi not enabled. bestie turn it on 😭
  • IWL_TOF_ENTRY_RESPONDER_OVERRIDE_PARAMS β€” Responder override the original parameters within the current session. plot twist params πŸ’œ

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h β€” that’s where this enum lives. Also the whole iconic 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)
  • 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)

Okay bestie, that’s the whole page πŸ’– Source/version: ./drivers/net/wireless/intel/i... and date: October 2026 β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from