drivers/net/wireless/ath/ath12k/wifi7/core.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/ath/ath12k/wifi7/core.c

Extension

.c

Size

1425 bytes

Lines

69

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• ../ahb.h
• ../pci.h
• pci.h
• ahb.h
• core.h
• dp.h
• ../debug.h

Detected Declarations

• function ath12k_wifi7_arch_init
• function ath12k_wifi7_arch_deinit
• function ath12k_wifi7_init
• function ath12k_wifi7_exit
• module init ath12k_wifi7_init

Annotated Snippet

module_init(ath12k_wifi7_init);
module_exit(ath12k_wifi7_exit);

MODULE_DESCRIPTION("Driver support for Qualcomm Technologies 802.11be WLAN devices");
MODULE_LICENSE("Dual BSD/GPL");

Annotation

• Immediate include surface: `linux/module.h`, `../ahb.h`, `../pci.h`, `pci.h`, `ahb.h`, `core.h`, `dp.h`, `../debug.h`.
• Detected declarations: `function ath12k_wifi7_arch_init`, `function ath12k_wifi7_arch_deinit`, `function ath12k_wifi7_init`, `function ath12k_wifi7_exit`, `module init ath12k_wifi7_init`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration 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.