drivers/net/wireless/mediatek/mt76/mt76x02_regs.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/mediatek/mt76/mt76x02_regs.h

Extension

.h

Size

22111 bytes

Lines

709

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 mt76_wcid_addr
• struct mt76_wcid_key
• enum mt76x02_cipher_type

Annotated Snippet

struct mt76_wcid_addr {
	u8 macaddr[6];
	__le16 ba_mask;
} __packed __aligned(4);

struct mt76_wcid_key {
	u8 key[16];
	u8 tx_mic[8];
	u8 rx_mic[8];
} __packed __aligned(4);

enum mt76x02_cipher_type {
	MT76X02_CIPHER_NONE,
	MT76X02_CIPHER_WEP40,
	MT76X02_CIPHER_WEP104,
	MT76X02_CIPHER_TKIP,
	MT76X02_CIPHER_AES_CCMP,
	MT76X02_CIPHER_CKIP40,
	MT76X02_CIPHER_CKIP104,
	MT76X02_CIPHER_CKIP128,
	MT76X02_CIPHER_WAPI,
};

#endif

Annotation

• Detected declarations: `struct mt76_wcid_addr`, `struct mt76_wcid_key`, `enum mt76x02_cipher_type`.
• 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.