drivers/net/wireless/ath/wil6210/pcie_bus.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/ath/wil6210/pcie_bus.c

Extension

.c

Size

17346 bytes

Lines

689

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.
• 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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/pci.h
• linux/moduleparam.h
• linux/interrupt.h
• linux/suspend.h
• wil6210.h
• linux/rtnetlink.h
• linux/pm_runtime.h

Detected Declarations

• function wil_set_capabilities
• function wil_disable_irq
• function wil_enable_irq
• function wil_remove_all_additional_vifs
• function wil_if_pcie_enable
• function wil_if_pcie_disable
• function wil_platform_rop_ramdump
• function wil_platform_rop_fw_recovery
• function wil_platform_ops_uninit
• function wil_pcie_probe
• function wil_pcie_remove
• function wil6210_suspend
• function wil6210_resume
• function wil6210_pm_notify
• function wil6210_pm_suspend
• function wil6210_pm_resume
• function wil6210_pm_runtime_idle
• function wil6210_pm_runtime_resume
• function wil6210_pm_runtime_suspend
• function wil6210_driver_init
• function wil6210_driver_exit
• module init wil6210_driver_init

Annotated Snippet

static struct pci_driver wil6210_driver = {
	.probe		= wil_pcie_probe,
	.remove		= wil_pcie_remove,
	.id_table	= wil6210_pcie_ids,
	.name		= WIL_NAME,
	.driver		= {
		.pm = &wil6210_pm_ops,
	},
};

static int __init wil6210_driver_init(void)
{
	int rc;

	rc = wil_platform_modinit();
	if (rc)
		return rc;

	rc = pci_register_driver(&wil6210_driver);
	if (rc)
		wil_platform_modexit();
	return rc;
}
module_init(wil6210_driver_init);

static void __exit wil6210_driver_exit(void)
{
	pci_unregister_driver(&wil6210_driver);
	wil_platform_modexit();
}
module_exit(wil6210_driver_exit);

MODULE_LICENSE("Dual BSD/GPL");
MODULE_AUTHOR("Qualcomm Atheros <wil6210@qca.qualcomm.com>");
MODULE_DESCRIPTION("Driver for 60g WiFi WIL6210 card");

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/moduleparam.h`, `linux/interrupt.h`, `linux/suspend.h`, `wil6210.h`, `linux/rtnetlink.h`, `linux/pm_runtime.h`.
• Detected declarations: `function wil_set_capabilities`, `function wil_disable_irq`, `function wil_enable_irq`, `function wil_remove_all_additional_vifs`, `function wil_if_pcie_enable`, `function wil_if_pcie_disable`, `function wil_platform_rop_ramdump`, `function wil_platform_rop_fw_recovery`, `function wil_platform_ops_uninit`, `function wil_pcie_probe`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern 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.