STRUCT IWL_TOF_RESPONDER_DYN_CONFIG_CMD_V2(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ struct iwl_tof_responder_dyn_config_cmd_v2(9) β€” the Kernel API Manual page, bestie edition πŸ¦‹

okay so this is a page from the Kernel API Manual, and it's about one little struct that handles your dynamic responder settings for Intel's fine timing measurement (FTM) stuff. it's giving "small struct, big job" energy, and honestly? we love that for it. πŸ’…


✨ NAME ✨

struct iwl_tof_responder_dyn_config_cmd_v2 β€” Dynamic responder settings πŸŽ€

no cap, that's the whole name and the whole job. she's concise. she's iconic.


🌸 SYNOPSIS 🌸

here's the actual shape of her, copy it exactly because structs are not a vibe-you-can-improvise situation:

struct iwl_tof_responder_dyn_config_cmd_v2 {
    __le32 lci_len;
    __le32 civic_len;
    u8 lci_civic[];
};

literally three members, one of them is a flexible array, and every single one of them matters. 🫢


πŸ’œ Members πŸ’œ

  • lci_len β€” The length of the 1st (LCI) part in the lci_civic buffer. yes bestie, it's the first part, and yes, the length field is how we know how much of the buffer is actually hers. πŸ”₯
  • civic_len β€” The length of the 2nd (CIVIC) part in the lci_civic buffer. second part, second length, same energy. πŸ’–
  • lci_civic β€” The LCI/CIVIC buffer, and this one has lore:
    • LCI data (if exists) comes first πŸ“
    • then, if needed, 0-padding such that the next part is dword-aligned 🧚
    • then CIVIC data (if exists) follows πŸŽ€
    • and then 0-padding again to complete a 4-multiple long buffer ⭐
okay so the whole alignment thing is not optional and not decorative β€” it's dword alignment, then padding out to a 4-multiple. do not skip the padding, do not "clean it up", do not pass go. πŸ™ˆ

🌈 SEE ALSO 🌈

this is the part where the man page just goes absolutely feral with cross-references, so buckle up bestie, we're listing every last 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)
  • 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)

like. fifty-something references. she said "you WILL understand the whole location API" and honestly? respect. 🧚✨


and that's the page!! πŸŽ€ this was pulled from ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h, dated October 2026, and it's filed under struct iwl_tof_responder_dyn_config_cmd_v2(9) β€” mwah, go read the rest of the kernel docs bestie, ily, bye πŸ’–πŸ‘‘

πŸ“¦ where this page comes from