drivers/net/wireless/ath/ath9k/init.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/ath/ath9k/init.c

Extension

.c

Size

30914 bytes

Lines

1166

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/dma-mapping.h
• linux/slab.h
• linux/module.h
• linux/of.h
• linux/of_net.h
• linux/nvmem-consumer.h
• linux/relay.h
• linux/dmi.h
• net/ieee80211_radiotap.h
• ath9k.h

Detected Declarations

• struct ath9k_eeprom_ctx
• function set_use_msi
• function ath9k_op_ps_wakeup
• function ath9k_op_ps_restore
• function ath9k_iowrite32
• function ath9k_ioread32
• function ath9k_multi_ioread32
• function __ath9k_reg_rmw
• function ath9k_reg_rmw
• function ath9k_reg_notifier
• function ath_descdma_setup
• function ath9k_init_queues
• function ath9k_init_misc
• function ath9k_init_pcoem_platform
• function ath9k_eeprom_request_cb
• function ath9k_eeprom_request
• function ath9k_eeprom_release
• function ath9k_nvmem_request_eeprom
• function AR9300_EEPROM_SIZE
• function ath9k_of_init
• function ath9k_init_softc
• function ath9k_init_band_txpower
• function ath9k_init_txpower_limits
• function ath9k_set_mcc_capab
• function ath9k_set_hw_capab
• function ath9k_init_device
• function ath9k_deinit_softc
• function ath9k_deinit_device
• function ath9k_init
• function ath9k_exit
• module init ath9k_init

Annotated Snippet

module_init(ath9k_init);

static void __exit ath9k_exit(void)
{
	is_ath9k_unloaded = true;
	ath_ahb_exit();
	ath_pci_exit();
	pr_info("%s: Driver unloaded\n", dev_info);
}
module_exit(ath9k_exit);

Annotation

• Immediate include surface: `linux/dma-mapping.h`, `linux/slab.h`, `linux/module.h`, `linux/of.h`, `linux/of_net.h`, `linux/nvmem-consumer.h`, `linux/relay.h`, `linux/dmi.h`.
• Detected declarations: `struct ath9k_eeprom_ctx`, `function set_use_msi`, `function ath9k_op_ps_wakeup`, `function ath9k_op_ps_restore`, `function ath9k_iowrite32`, `function ath9k_ioread32`, `function ath9k_multi_ioread32`, `function __ath9k_reg_rmw`, `function ath9k_reg_rmw`, `function ath9k_reg_notifier`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.