STRUCT IWL_GEO_TX_POWER_PROFILES_CMD_V3(9)
π struct iwl_geo_tx_power_profiles_cmd_v3(9) β Kernel API Manual, bestie edition
okay so this is a page from the Kernel API Manual and honestly? it's giving "niche wireless struct that lowkey runs the vibes." we're talking about struct iwl_geo_tx_power_profiles_cmd_v3 β not the v1, not the v2, the v3 β and it's the struct for PER_CHAIN_LIMIT_OFFSET_CMD. yes that's a mouthful, no you don't have to say it out loud. π«Ά
β¨ NAME β¨
struct iwl_geo_tx_power_profiles_cmd_v3 β literally the struct for PER_CHAIN_LIMIT_OFFSET_CMD cmd. that's it, that's the whole name section, she's concise π
π¦ SYNOPSIS π¦
struct iwl_geo_tx_power_profiles_cmd_v3 {
__le32 ops;
struct iwl_per_chain_offset
table[IWL_NUM_GEO_PROFILES][IWL_NUM_BANDS_PER_CHAIN_V2];
__le32 table_revision;
};
yes the indentation in the table line is Like That, we don't fix it, we respect it, it's iconic in a weird way π
π Members π
opsβ the operations field, and its value comes fromenum iwl_geo_per_chain_offset_operation. so like, what are we even doing here? that enum knows.tableβ the offset profile per band. it's a whole 2D situation:[IWL_NUM_GEO_PROFILES][IWL_NUM_BANDS_PER_CHAIN_V2]ofstruct iwl_per_chain_offset. main character array energy fr fr πtable_revisionβ okay so the value is0for not-South Korea and1for South Korea. and the name? the name is misleading. not me side-eyeing this field π the docs literally say it β "(the name is misleading)" β so don't come for me, come for the field name.
πΈ SEE ALSO πΈ
the kernel file it lives in: ./drivers/net/wireless/intel/iwlwifi/fw/api/power.h
and now the whole friend group, no cap, everybody's invited to the group chat:
enum iwl_ltr_config_flags(9)struct iwl_ltr_config_cmd_v1(9)struct iwl_ltr_config_cmd(9)enum iwl_power_flags(9)struct iwl_powertable_cmd(9)enum iwl_device_power_flags(9)struct iwl_device_power_cmd(9)struct iwl_mac_power_cmd_v2(9)struct iwl_mac_power_cmd(9)struct iwl_dev_tx_power_common(9)struct iwl_dev_tx_power_cmd_v3(9)struct iwl_dev_tx_power_cmd_v4(9)struct iwl_dev_tx_power_cmd_v5(9)struct iwl_dev_tx_power_cmd_v8(9)struct iwl_dev_tx_power_cmd_v3_v8(9)struct iwl_dev_tx_power_cmd_v9(9)struct iwl_dev_tx_power_cmd_v10(9)enum iwl_geo_per_chain_offset_operation(9)struct iwl_per_chain_offset(9)struct iwl_geo_tx_power_profiles_cmd_v1(9)struct iwl_geo_tx_power_profiles_cmd_v2(9)struct iwl_geo_tx_power_profiles_cmd_v4(9)struct iwl_geo_tx_power_profiles_cmd_v5(9)struct iwl_geo_tx_power_profiles_cmd_v6(9)struct iwl_geo_tx_power_profiles_resp(9)enum iwl_ppag_flags(9)union iwl_ppag_table_cmd(9)struct iwl_sar_offset_mapping_cmd(9)struct iwl_beacon_filter_cmd(9)struct iwl_txpower_constraints_cmd(9)
like, thirty entries. she's social. she knows everybody. iykyk β¨
ngl the whole v1-through-v6 family tree is a lot, but that's the lore and we're keeping it π§
and that's the page, bestie!! source was ./drivers/net/wireless/intel/i... (yes it's truncated in the original, we keep the truncation, we don't invent the rest π), dated October 2026, and this whole thing is struct iwl_...files_cmd_v3(9) in the Kernel API Manual. slay, go read some power.h, ily, 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