ENUM IWL_TOF_BANDWIDTH(9)
π¦ enum iwl_tof_bandwidth(9) β the Kernel API Manual, section 9, bestie β¨
okay so picture this: you're deep in the Intel wireless driver, section 9 of the kernel API manual, and you hit a field called bandwidth inside iwl_tof_range_req_ap_entry β and it's not a number, it's this enum. so iconic of it. this whole page is just the menu of legal values that field can take. no cap, that's the entire vibe. π
β¨ NAME β¨
enum iwl_tof_bandwidth β the values you're allowed to shove into iwl_tof_range_req_ap_entry.bandwidth. that's it, that's the job. π
πΈ SYNOPSIS πΈ
enum iwl_tof_bandwidth {
IWL_TOF_BW_20_LEGACY ,
IWL_TOF_BW_20_HT ,
IWL_TOF_BW_40 ,
IWL_TOF_BW_80 ,
IWL_TOF_BW_160 ,
IWL_TOF_BW_NUM
};
like, look at her. six constants, zero drama, all business. π«Ά
π Constants π
bestie these are the actual members, in order, no skipping:
IWL_TOF_BW_20_LEGACYβ 20 MHz non-HT. the old-school 20, no fancy high-throughput stuff attached. she's giving vintage. π°οΈIWL_TOF_BW_20_HTβ 20 MHz HT. same 20 MHz width, but this one's high-throughput flavored. β¨IWL_TOF_BW_40β 40 MHz. double the width, double the main character energy. π₯IWL_TOF_BW_80β 80 MHz. now we're cooking. πIWL_TOF_BW_160β 160 MHz. the big one. absolute unit of a channel. πIWL_TOF_BW_NUMβ the count of tof bandwidths. she's not a bandwidth herself, she's the number of them β the boundary marker at the end, iykyk. π§
fr fr keep IWL_TOF_BW_NUM last and don't treat it as a real bandwidth β it's literally just "how many are there". π
π SEE ALSO π
lowkey the longest see-also list you've ever seen and honestly? she ate. everything below lives in the kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h β that's the enum's home address, bestie. π‘
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_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)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, bestie π this lil artifact ships out of ./drivers/net/wireless/intel/i... and the date on the tin is October 2026 β so like, future energy. go read your enums, you got this, periodt. πππ¦
π¦ 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