ENUM IWL_NVM_CHANNEL_FLAGS(9)

💅 NAME 💅

okay so this is enum iwl_nvm_channel_flags — channel flags in NVM, bestie. that's the whole vibe. it's from the Kernel API Manual (yes, that manual) and it's literally just a big list of channel flags and what each one means. no cap.

✨ SYNOPSIS ✨

here's the whole enum, copied exactly bc we do not mess with identifiers in this house:

enum iwl_nvm_channel_flags {
    NVM_CHANNEL_VALID ,
    NVM_CHANNEL_IBSS ,
    NVM_CHANNEL_ALLOW_20MHZ_ACTIVITY ,
    NVM_CHANNEL_ACTIVE ,
    NVM_CHANNEL_RADAR ,
    NVM_CHANNEL_INDOOR_ONLY ,
    NVM_CHANNEL_GO_CONCURRENT ,
    NVM_CHANNEL_UNIFORM ,
    NVM_CHANNEL_20MHZ ,
    NVM_CHANNEL_40MHZ ,
    NVM_CHANNEL_80MHZ ,
    NVM_CHANNEL_160MHZ ,
    NVM_CHANNEL_DC_HIGH ,
    NVM_CHANNEL_VLP ,
    NVM_CHANNEL_AFC ,
    NVM_CHANNEL_VLP_AP_NOT_ALLOWED

};

sixteen constants, zero skips. slay.

🎀 CONSTANTS 🎀

okay bestie, this is the part you actually came for. one by one, no gatekeeping:

• NVM_CHANNEL_VALID — this channel is usable for this SKU/geo. like, it passed the vibe check for your region. 🦋
• NVM_CHANNEL_IBSS — usable as an IBSS channel, and deprecated when IWL_NVM_SBANDS_FLAGS_LAR is enabled. that's a real caveat, don't @ me.
• NVM_CHANNEL_ALLOW_20MHZ_ACTIVITY — active scanning allowed, and AP allowed only in 20 MHz. Valid only when IWL_NVM_SBANDS_FLAGS_LAR is enabled. twenty only, no extras. 💅
• NVM_CHANNEL_ACTIVE — active scanning allowed, and it also allows IBSS when IWL_NVM_SBANDS_FLAGS_LAR is enabled. see the pattern? that flag is everywhere, iykyk.
• NVM_CHANNEL_RADAR — radar detection required 👀 like, the hardware has to actually check for radar before it goes off. not optional.
• NVM_CHANNEL_INDOOR_ONLY — only indoor use is allowed. literally no going outside with this one, it's giving house cat. 🙈
• NVM_CHANNEL_GO_CONCURRENT — GO operation is allowed when connected to BSS on same channel on 2.4 or same UNII band on 5.2. ok that sentence is a mouthful but it's exactly what it says, don't water it down.
• NVM_CHANNEL_UNIFORM — uniform spreading required. spread out, bestie. 🌈
• NVM_CHANNEL_20MHZ — 20 MHz channel okay ✨
• NVM_CHANNEL_40MHZ — 40 MHz channel okay ✨
• NVM_CHANNEL_80MHZ — 80 MHz channel okay ✨
• NVM_CHANNEL_160MHZ — 160 MHz channel okay ✨ (look at her go, iconic width progression)
• NVM_CHANNEL_DC_HIGH — DC HIGH required/allowed (?). yes the question mark is in the original. we keep it. we do not edit the source's confusion, we simply respect it. 💀
• NVM_CHANNEL_VLP — client support connection to UHB VLP AP. 🫶
• NVM_CHANNEL_AFC — client support connection to UHB AFC AP. 🫶
• NVM_CHANNEL_VLP_AP_NOT_ALLOWED — UHB VLP AP not allowed, and valid only when NVM_CHANNEL_VLP is enabled. so it only even means anything when its bestie is turned on, periodt.

fr fr though: a few of these carry real conditions — IWL_NVM_SBANDS_FLAGS_LAR gating, the deprecation on NVM_CHANNEL_IBSS, the NVM_CHANNEL_VLP dependency — those aren't decoration, they're the whole point. read them twice. 😭

🦋 SEE ALSO 🦋

go read these next, bestie, they're all in the same orbit:

• Kernel file ./drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.h
• enum iwl_nvm_sbands_flags(9)
• enum iwl_puncturing_status(9)
• struct iwl_reg_capa(9)
• iwl_parse_nvm_mcc_info(9)
• struct iwl_nvm_section(9)
• iwl_read_external_nvm(9)

and that's the page!! 🎀 source path was ./drivers/net/wireless/intel/i... (yes it's truncated, that's how it came, i don't make the rules), dated October 2026, filed under enum iwl_nvm_channel_flags(9) in the Kernel API Manual. go be iconic with your channels, mwah 💜✨