STRUCT IWL_TOF_RANGE_RSP_AP_ENTRY_NTFY_V4(9)
π struct iwl_tof_range_rsp_ap_entry_ntfy_v4(9) π
okay so bestie, this is a Kernel API Manual page β yes, another one β and it's all about struct iwl_tof_range_rsp_ap_entry_ntfy_v4. Cute name, I know. The manual name is struct iwl_...ntry_ntfy_v4(9) because apparently even doc generators get tired of typing the whole thing π. Anyway. Let's get into it.
β¨ NAME β¨
struct iwl_tof_range_rsp_ap_entry_ntfy_v4 β literally just: AP parameters (response). That's the vibe. π
πΈ SYNOPSIS πΈ
Here's the whole struct, character for character, no cap, don't touch it:
struct iwl_tof_range_rsp_ap_entry_ntfy_v4 {
u8 bssid[ETH_ALEN];
u8 measure_status;
u8 measure_bw;
__le32 rtt;
__le32 rtt_variance;
__le32 rtt_spread;
s8 rssi;
u8 rssi_spread;
u8 last_burst;
u8 refusal_period;
__le32 timestamp;
__le32 start_tsf;
__le32 rx_rate_n_flags;
__le32 tx_rate_n_flags;
__le32 t2t3_initiator;
__le32 t1t4_responder;
__le16 common_calib;
__le16 specific_calib;
__le32 papd_calib_output;
};
π¦ Members π¦
okay so here's the field-by-field breakdown, and I'm gonna be so real with you, every single one is here π
bssidβ the BSSID of the AP. its little name tag π·οΈmeasure_statusβ the current AP's measurement status, and it's one ofenum iwl_tof_entry_status. iykyk.measure_bwβ the current AP Bandwidth, and the mapping is0= 20MHz,1= 40MHz,2= 80MHz. slay, we love a numbered list.rttβ The Round Trip Time that it took for the last measurement for the current AP[pSec]. picoseconds, bestie, we're measuring everything.rtt_varianceβ The Variance of the RTT values measured for the current AP.rtt_spreadβ The Difference between the maximum and the minimum RTT values measured for the current AP in the current session[pSec].rssiβ RSSI as uploaded in the Channel Estimation notification.rssi_spreadβ The Difference between the maximum and the minimum RSSI values measured for the current AP in the current session.last_burstβ1if no more FTM sessions are scheduled for this responder. like, we're done here, bye πrefusal_periodβ refusal period in case ofIWL_TOF_ENTRY_RESPONDER_CANNOT_COLABORATE[sec]. (yes,COLABORATEβ one L β that's how it's spelled in the original and I'm not fixing it π)timestampβ The GP2 Clock[usec]where the Channel Estimation notification was uploaded by the LMAC.start_tsfβ measurement start time in TSF of the mac specified in the range request.rx_rate_n_flagsβ rate and flags of the last FTM frame received from this responder.tx_rate_n_flagsβ rate and flags of the last ack sent to this responder.t2t3_initiatorβ as calculated from the algo in the initiator. main character math βt1t4_responderβ as calculated from the algo in the responder. supporting cast math π«Άcommon_calibβ Calib val that was used in for this AP measurement. (again β "used in for" β verbatim, not me, don't come for me π)specific_calibβ val that was used in for this AP measurement.papd_calib_outputβ The result of the tof papd calibration that was injected into the algorithm. injected, like a truth bomb π
π SEE ALSO π
the friend group. the whole crew. everyone shows up:
- 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_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_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)
bestie real talk: this page came from./drivers/net/wireless/intel/i...with the dateOctober 2026, and the header/footer both saystruct iwl_...ntry_ntfy_v4(9). that's the whole source situation, mwah π
and that's the page!! you now know more about AP range response entries than like 99% of people. iconic. go take a nap, you earned it π§π
π¦ 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