ENUM IWL_TOF_RESPONDER_CMD_VALID_FIELD(9)

okay so real talk: this is the manual page for enum iwl_tof_responder_cmd_valid_field(9) from the Kernel API Manual, and it's genuinely just a little enum that answers one question — which fields in the responder cfg actually count as valid? Every constant below is a "yes, this field is legit" flag. That's the whole vibe. 🎀

✨ NAME ✨

enum iwl_tof_responder_cmd_valid_field — the valid fields in the responder cfg, bestie. That's it. That's the enum. 💅

🦋 SYNOPSIS 🦋

enum iwl_tof_responder_cmd_valid_field {
    IWL_TOF_RESPONDER_CMD_VALID_CHAN_INFO ,
    IWL_TOF_RESPONDER_CMD_VALID_TOA_OFFSET ,
    IWL_TOF_RESPONDER_CMD_VALID_COMMON_CALIB ,
    IWL_TOF_RESPONDER_CMD_VALID_SPECIFIC_CALIB ,
    IWL_TOF_RESPONDER_CMD_VALID_BSSID ,
    IWL_TOF_RESPONDER_CMD_VALID_TX_ANT ,
    IWL_TOF_RESPONDER_CMD_VALID_ALGO_TYPE ,
    IWL_TOF_RESPONDER_CMD_VALID_NON_ASAP_SUPPORT ,
    IWL_TOF_RESPONDER_CMD_VALID_STATISTICS_REPORT_SUPPORT ,
    IWL_TOF_RESPONDER_CMD_VALID_MCSI_NOTIF_SUPPORT ,
    IWL_TOF_RESPONDER_CMD_VALID_FAST_ALGO_SUPPORT ,
    IWL_TOF_RESPONDER_CMD_VALID_RETRY_ON_ALGO_FAIL ,
    IWL_TOF_RESPONDER_CMD_VALID_STA_ID ,
    IWL_TOF_RESPONDER_CMD_VALID_NDP_SUPPORT ,
    IWL_TOF_RESPONDER_CMD_VALID_NDP_PARAMS ,
    IWL_TOF_RESPONDER_CMD_VALID_LMR_FEEDBACK ,
    IWL_TOF_RESPONDER_CMD_VALID_SESSION_ID ,
    IWL_TOF_RESPONDER_CMD_VALID_BSS_COLOR ,
    IWL_TOF_RESPONDER_CMD_VALID_MIN_MAX_TIME_BETWEEN_MSR

};

🌸 CONSTANTS 🌸

All nineteen of them, in order, no skips — we do not leave the group chat on read. 🫶

• IWL_TOF_RESPONDER_CMD_VALID_CHAN_INFO — the channel info field is valid, slay.
• IWL_TOF_RESPONDER_CMD_VALID_TOA_OFFSET — the ToA offset field is valid.
• IWL_TOF_RESPONDER_CMD_VALID_COMMON_CALIB — common calibration mode? valid.
• IWL_TOF_RESPONDER_CMD_VALID_SPECIFIC_CALIB — specific calibration mode is valid (the source spells it "spefici" and honestly? iconic, we're keeping it 💀).
• IWL_TOF_RESPONDER_CMD_VALID_BSSID — BSSID is valid.
• IWL_TOF_RESPONDER_CMD_VALID_TX_ANT — the TX antenna is valid.
• IWL_TOF_RESPONDER_CMD_VALID_ALGO_TYPE — the algorithm type is valid.
• IWL_TOF_RESPONDER_CMD_VALID_NON_ASAP_SUPPORT — non-ASAP support is valid.
• IWL_TOF_RESPONDER_CMD_VALID_STATISTICS_REPORT_SUPPORT — statistics report support is valid.
• IWL_TOF_RESPONDER_CMD_VALID_MCSI_NOTIF_SUPPORT — MCSI notification support is valid.
• IWL_TOF_RESPONDER_CMD_VALID_FAST_ALGO_SUPPORT — fast algorithm support is valid.
• IWL_TOF_RESPONDER_CMD_VALID_RETRY_ON_ALGO_FAIL — retry on algorithm failure is valid.
• IWL_TOF_RESPONDER_CMD_VALID_STA_ID — the station ID is valid.
• IWL_TOF_RESPONDER_CMD_VALID_NDP_SUPPORT — the enable/disable NDP ranging support field is valid.
• IWL_TOF_RESPONDER_CMD_VALID_NDP_PARAMS — the NDP parameters are valid.
• IWL_TOF_RESPONDER_CMD_VALID_LMR_FEEDBACK — LMR feedback support is valid.
• IWL_TOF_RESPONDER_CMD_VALID_SESSION_ID — the session id flag is valid.
• IWL_TOF_RESPONDER_CMD_VALID_BSS_COLOR — the bss_color field is valid.
• IWL_TOF_RESPONDER_CMD_VALID_MIN_MAX_TIME_BETWEEN_MSR — the min_time_between_msr and max_time_between_msr fields are valid.

🔥 SEE ALSO 🔥

Lives in the kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h, and it has so many neighbors — the whole ToF friend group. Not me listing every single one, but also… yes, every single one, because we don't gatekeep:

• 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_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_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)

and that's the whole page, no notes 💜 source/version is ./drivers/net/wireless/intel/i... and the date on this one is October 2026 — so yeah, it's giving future-dated manual page energy, and the manual name enum iwl_tof..._valid_field(9) is literally right up top if you need to cite it. bye bestie, go make those responder cfg fields valid ✨🦋🎀