drivers/net/wireless/mediatek/mt76/mt76x2/pci.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/mediatek/mt76/mt76x2/pci.c

Extension

.c

Size

4359 bytes

Lines

188

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/module.h
• linux/pci.h
• mt76x2.h

Detected Declarations

• function mt76x2e_probe
• function mt76x2e_remove
• function mt76x2e_suspend
• function mt76x2e_resume
• function mt76_for_each_q_rx

Annotated Snippet

static struct pci_driver mt76pci_driver = {
	.name		= KBUILD_MODNAME,
	.id_table	= mt76x2e_device_table,
	.probe		= mt76x2e_probe,
	.remove		= mt76x2e_remove,
#ifdef CONFIG_PM
	.suspend	= mt76x2e_suspend,
	.resume		= mt76x2e_resume,
#endif /* CONFIG_PM */
};

module_pci_driver(mt76pci_driver);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `mt76x2.h`.
• Detected declarations: `function mt76x2e_probe`, `function mt76x2e_remove`, `function mt76x2e_suspend`, `function mt76x2e_resume`, `function mt76_for_each_q_rx`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.