drivers/net/wireless/intel/iwlwifi/fw/api/txq.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/intel/iwlwifi/fw/api/txq.h

Extension

.h

Size

4105 bytes

Lines

128

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct iwl_tx_queue_cfg_cmd
• struct iwl_tx_queue_cfg_rsp
• enum iwl_mvm_dqa_txq
• enum iwl_mvm_tx_fifo
• enum iwl_gen2_tx_fifo
• enum iwl_bz_tx_fifo
• enum iwl_tx_queue_cfg_actions

Annotated Snippet

struct iwl_tx_queue_cfg_cmd {
	u8 sta_id;
	u8 tid;
	__le16 flags;
	__le32 cb_size;
	__le64 byte_cnt_addr;
	__le64 tfdq_addr;
} __packed; /* TX_QUEUE_CFG_CMD_API_S_VER_2 */

/**
 * struct iwl_tx_queue_cfg_rsp - response to txq hw scheduler config
 * @queue_number: queue number assigned to this RA -TID
 * @flags: set on failure
 * @write_pointer: initial value for write pointer
 * @reserved: reserved
 */
struct iwl_tx_queue_cfg_rsp {
	__le16 queue_number;
	__le16 flags;
	__le16 write_pointer;
	__le16 reserved;
} __packed; /* TX_QUEUE_CFG_RSP_API_S_VER_2 */

#endif /* __iwl_fw_api_txq_h__ */

Annotation

• Detected declarations: `struct iwl_tx_queue_cfg_cmd`, `struct iwl_tx_queue_cfg_rsp`, `enum iwl_mvm_dqa_txq`, `enum iwl_mvm_tx_fifo`, `enum iwl_gen2_tx_fifo`, `enum iwl_bz_tx_fifo`, `enum iwl_tx_queue_cfg_actions`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.