STRUCT IWL_TOF_RANGE_REQ_CMD_V5(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Hii bestie!! Welcome to struct iwl_tof_range_req_cmd_v5(9) from the Kernel API Manual β€” this page is literally about the start measurement cmd, and we’re gonna get you comfy with every single field. No skipping, no vibes-only summary. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

Here’s the struct in all its glory, bestie β€” copy-paste exact:

struct iwl_tof_range_req_cmd_v5 {
    __le32 initiator_flags;
    u8 request_id;
    u8 initiator;
    u8 one_sided_los_disable;
    u8 req_timeout;
    u8 report_policy;
    u8 reserved0;
    u8 num_of_ap;
    u8 macaddr_random;
    u8 range_req_bssid[ETH_ALEN];
    u8 macaddr_template[ETH_ALEN];
    u8 macaddr_mask[ETH_ALEN];
    u8 ftm_rx_chains;
    u8 ftm_tx_chains;
    __le16 common_calib;
    __le16 specific_calib;
    struct iwl_tof_range_req_ap_entry_v2 ap[IWL_TOF_MAX_APS];
};

🌸 Members 🌸

Okay, member-by-member, and yes we’re doing all of them:

  • initiator_flags β€” see flags iwl_tof_initiator_flags
  • request_id β€” A Token incremented per request. The same Token will be sent back in the range response
  • initiator β€” 0- NW initiated, 1 - Client Initiated
  • one_sided_los_disable β€” this manpage lists the field but gives no extra description here, so we’re not inventing one πŸ™ˆ
  • req_timeout β€” Requested timeout of the response in units of 100ms. This is equivalent to the session time configured to the LMAC in Initiator Request
  • report_policy β€” Supported partially for this release: For current release - the range report will be uploaded as a batch when ready or when the session is done (successfully / partially). one of iwl_tof_response_mode.
  • reserved0 β€” reserved
  • num_of_ap β€” Number of APs to measure (error if > IWL_TOF_MAX_APS)
  • macaddr_random β€” this manpage lists the field but gives no extra description here either, bestie, so no cap on staying accurate πŸ’…
  • range_req_bssid β€” ranging request BSSID
  • macaddr_template β€” MAC address template to use for non-randomized bits
  • macaddr_mask β€” Bits set to 0 shall be copied from the MAC address template. Bits set to 1 shall be randomized by the UMAC
  • ftm_rx_chains β€” Rx chain to open to receive Responder’s FTMs (XVT)
  • ftm_tx_chains β€” Tx chain to send the ack to the Responder FTM (XVT)
  • common_calib β€” The common calib value to inject to this measurement calc
  • specific_calib β€” The specific calib value to inject to this measurement calc
  • ap β€” per-AP request data

πŸ‘‘ SEE ALSO πŸ‘‘

Bestie, the cross-refs are iconic β€” here’s every single one:

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

Cute sign-off time: the footer’s source/version bit is ./drivers/net/wireless/intel/i..., the date is October 2026, and the page title down there is struct iwl_...e_req_cmd_v5(9). Bye bestie, go slay those range requests! πŸ’…πŸ’–

πŸ“¦ where this page comes from