STRUCT IWL_TOF_RANGE_RSP_AP_ENTRY_NTFY(9)
๐ struct iwl_tof_range_rsp_ap_entry_ntfy(9) ๐
okay bestie, welcome to the Kernel API Manual โจ this one's all about struct iwl_tof_range_rsp_ap_entry_ntfy and honestly? she's giving "receipts from the AP" energy ๐
๐ธ NAME ๐ธ
struct iwl_tof_range_rsp_ap_entry_ntfy โ AP parameters (response), periodt ๐
โจ SYNOPSIS โจ
like, here's her whole shape, no cap, copy it exactly:
struct iwl_tof_range_rsp_ap_entry_ntfy {
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 reserved1[2];
__le32 t2t3_initiator;
__le32 t1t4_responder;
__le16 common_calib;
__le16 specific_calib;
__le32 papd_calib_output;
u8 rttConfidence;
u8 reserved[3];
u8 rx_pn[IEEE80211_CCMP_PN_LEN];
u8 tx_pn[IEEE80211_CCMP_PN_LEN];
};
๐ฆ Members ๐ฆ
okay so every single field, one by one, let's go ๐ซถ
bssidโ the BSSID of the AP ๐ซ literally just which AP we're talking about.measure_statusโ current AP's measurement status, one ofenum iwl_tof_entry_status. bestie's mood ring, basically ๐measure_bwโ Current AP Bandwidth:020MHz,140MHz,280MHz๐ก (yes those are the actual numbers, don't @ me)rttโ The Round Trip Time that took for the last measurement for current AP[pSec]โฑ๏ธrtt_varianceโ The Variance of the RTT values measured for current AP. she's not consistent, and that's the tea ๐rtt_spreadโ The Difference between the maximum and the minimum RTT values measured for current AP in the current session[pSec]๐ญ the range of the chaos.rssiโ RSSI as uploaded in the Channel Estimation notification ๐ถrssi_spreadโ The Difference between the maximum and the minimum RSSI values measured for current AP in the current session. same vibe check, but for signal ๐ฅlast_burstโ1if no more FTM sessions are scheduled for this responder ๐ like, that's a wrap, we're done here.refusal_periodโ refusal period in case ofIWL_TOF_ENTRY_RESPONDER_CANNOT_COLABORATE[sec]๐ the AP said "not today" and this is how long they're on read.timestampโ The GP2 Clock[usec]where Channel Estimation notification was uploaded by the LMAC โฐstart_tsfโ measurement start time in TSF of the mac specified in the range request ๐ฐ๏ธreserved1โ reserved, for backwards compatibility ๐ (she's just sitting there so old code doesn't break, iconic behavior honestly)t2t3_initiatorโ as calculated from the algo in the initiator ๐งฎt1t4_responderโ as calculated from the algo in the responder ๐งฎcommon_calibโ Calib val that was used in for this AP measurement โจ (yes, the wording is literally "used in for", we keep it, we don't fix it, we respect her)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. ๐ algorithm said "thank u for the data".rttConfidenceโ a value between0-31that represents the rtt accuracy ๐ lowkey how much you should trust her.reservedโ for alignment ๐ (padding squads, always on duty)rx_pnโ the last PN used for this responder Rx in case PMF is configured in LE byte order ๐tx_pnโ the last PN used for this responder Tx in case PMF is configured in LE byte order ๐
๐ SEE ALSO ๐
okay the friend group is HUGE, here's everyone tagged in the group chat ๐ฑ
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_v4(9), struct iwl_tof_range_rsp_ap_entry_ntfy_v5(9), struct iwl_tof_range_rsp_ap_entry_ntfy_v7(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) ๐
ngl bestie, that's the whole page. every field, every unit, every "used in for" โ nothing skipped, we ate and left no crumbs ๐
mwah ๐ this came from ./drivers/net/wireless/intel/i... and it's dated October 2026, so like, see u in the future, and remember: struct iwl_tof_range_rsp_ap_entry_ntfy(9) forever ๐
๐ฆ 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