STRUCT IWL_FW_DBG_TRIGGER_BA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct iwl_fw_dbg_trigger_ba β€” the Kernel API Manual moment

okay so bestie, you're in the Kernel API Manual and today's main character is struct iwl_fw_dbg_trigger_ba β€” it's the little struct that configures BlockAck related trigger stuff. no cap, that's literally its whole job. πŸŽ€


✨ NAME ✨

struct iwl_fw_dbg_trigger_ba β€” configures BlockAck related trigger πŸ’«


🌸 SYNOPSIS 🌸

struct iwl_fw_dbg_trigger_ba {
    __le16 rx_ba_start;
    __le16 rx_ba_stop;
    __le16 tx_ba_start;
    __le16 tx_ba_stop;
    __le16 rx_bar;
    __le16 tx_bar;
    __le16 frame_timeout;
 };

like, look at her. seven __le16 fields, all lined up, all iconic. πŸ‘‘


πŸ¦‹ Members πŸ¦‹

heads up bestie: every single one of these is a tid bitmap β€” that's the whole vibe. the bitmap is what you configure to pick which tid the trigger should fire on. 🫢
  • rx_ba_start β€” tid bitmap to configure on what tid the trigger should occur when an Rx BlockAck session is started. go off, session start. πŸ”₯
  • rx_ba_stop β€” tid bitmap to configure on what tid the trigger should occur when an Rx BlockAck session is stopped. bye bestie, trigger fires. 😭
  • tx_ba_start β€” tid bitmap to configure on what tid the trigger should occur when a Tx BlockAck session is started. twin of the one above, but Tx. ✨
  • tx_ba_stop β€” tid bitmap to configure on what tid the trigger should occur when a Tx BlockAck session is stopped. the closing-act energy fr fr. πŸ’…
  • rx_bar β€” tid bitmap to configure on what tid the trigger should occur when a BAR is received (for a Tx BlockAck session). yes, received, and yes, it's the Tx session β€” that's not a typo, that's just how she is. πŸ™ˆ
  • tx_bar β€” tid bitmap to configure on what tid the trigger should occur when a BAR is send (for an Rx BlocAck session). (that "send" and that "BlocAck" are exactly how the original spells it β€” copying her spelling verbatim because I respect her πŸ’–)
  • frame_timeout β€” tid bitmap to configure on what tid the trigger should occur when a frame times out in the reordering buffer. the sad one. the dramatic one. the "omg where did you go" one. πŸ’€

🌈 SEE ALSO 🌈

the whole group chat, honestly. all of these are canon:

Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/file.h enum β€” that's where she lives 🏠

  • iwl_ucode_tlv_flag(9)
  • iwl_ucode_tlv_api(9)
  • iwl_ucode_tlv_capa(9)
  • iwl_tlv_calib_ctrl(9)
  • iwl_fw_dbg_reg_op(9)
  • iwl_fw_dbg_monitor_mode(9)
  • iwl_fw_dbg_mem_seg_tlv(9)
  • iwl_fw_dbg_dest_tlv_v1(9)
  • iwl_fw_dbg_trigger_mode(9)
  • iwl_fw_dbg_trigger_flags(9)
  • iwl_fw_dbg_trigger_vif_type(9)
  • iwl_fw_dbg_trigger_tlv(9)
  • iwl_fw_dbg_trigger_missed_bcon(9)
  • iwl_fw_dbg_trigger_cmd(9)
  • iwl_fw_dbg_trigger_stats(9)
  • iwl_fw_dbg_trigger_low_rssi(9)
  • iwl_fw_dbg_trigger_mlme(9)
  • iwl_fw_dbg_trigger_txq_timer(9)
  • iwl_fw_dbg_trigger_time_event(9)
  • iwl_fw_dbg_trigger_tdls(9)
  • iwl_fw_dbg_trigger_tx_status(9)
  • iwl_fw_dbg_conf_tlv(9)
  • iwl_fw_cmd_version(9)
  • iwl_fw_cmd_bios_table(9)

a whole friend group. read them all, iykyk. πŸ“šπŸ’œ


mwah πŸ’‹ that's the page! sourced straight from ./drivers/net/wireless/intel/i... and dated October 2026 β€” so she's from the future, obviously, and she's still struct iwl_f...g_trigger_ba(9) at heart. slay, periodt, go configure your tid bitmaps responsibly. 🧚⭐

πŸ“¦ where this page comes from