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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

20429 bytes

Lines

709

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
• mt7925.h
• mac.h
• mcu.h
• regd.h
• ../dma.h

Detected Declarations

• function mt7925e_init_reset
• function mt7925e_unregister_device
• function mt7925_reg_remap_restore
• function mt7925_reg_map_l1
• function mt7925_reg_map_l2
• function __mt7925_reg_addr
• function mt7925_rr
• function mt7925_wr
• function mt7925_rmw
• function mt7927_dma_init
• function mt7925_dma_init
• function mt7925_pci_probe
• function mt7925_pci_remove
• function mt7925_pci_suspend
• function mt76_for_each_q_rx
• function _mt7925_pci_resume
• function mt76_for_each_q_rx
• function mt7925_pci_shutdown
• function mt7925_pci_resume
• function mt7925_pci_restore

Annotated Snippet

static struct pci_driver mt7925_pci_driver = {
	.name		= KBUILD_MODNAME,
	.id_table	= mt7925_pci_device_table,
	.probe		= mt7925_pci_probe,
	.remove		= mt7925_pci_remove,
	.shutdown       = mt7925_pci_shutdown,
	.driver.pm	= pm_sleep_ptr(&mt7925_pm_ops),
};

module_pci_driver(mt7925_pci_driver);

MODULE_DEVICE_TABLE(pci, mt7925_pci_device_table);
MODULE_FIRMWARE(MT7925_FIRMWARE_WM);
MODULE_FIRMWARE(MT7925_ROM_PATCH);
MODULE_FIRMWARE(MT7927_FIRMWARE_WM);
MODULE_FIRMWARE(MT7927_ROM_PATCH);
MODULE_AUTHOR("Deren Wu <deren.wu@mediatek.com>");
MODULE_AUTHOR("Lorenzo Bianconi <lorenzo@kernel.org>");
MODULE_DESCRIPTION("MediaTek MT7925E (PCIe) wireless driver");
MODULE_LICENSE("Dual BSD/GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `mt7925.h`, `mac.h`, `mcu.h`, `regd.h`, `../dma.h`.
• Detected declarations: `function mt7925e_init_reset`, `function mt7925e_unregister_device`, `function mt7925_reg_remap_restore`, `function mt7925_reg_map_l1`, `function mt7925_reg_map_l2`, `function __mt7925_reg_addr`, `function mt7925_rr`, `function mt7925_wr`, `function mt7925_rmw`, `function mt7927_dma_init`.
• 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.