drivers/net/wireless/realtek/rtlwifi/rtl8188ee/sw.c

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/realtek/rtlwifi/rtl8188ee/sw.c

Extension

.c

Size

12753 bytes

Lines

391

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.
• 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

• ../wifi.h
• ../core.h
• ../pci.h
• reg.h
• def.h
• phy.h
• dm.h
• hw.h
• trx.h
• led.h
• table.h
• linux/vmalloc.h
• linux/module.h

Detected Declarations

• function rtl88e_init_aspm_vars
• function rtl88e_init_sw_vars
• function rtl88e_deinit_sw_vars
• function rtl88e_get_btc_status

Annotated Snippet

static struct pci_driver rtl88ee_driver = {
	.name = KBUILD_MODNAME,
	.id_table = rtl88ee_pci_ids,
	.probe = rtl_pci_probe,
	.remove = rtl_pci_disconnect,
	.driver.pm = &rtlwifi_pm_ops,
};

module_pci_driver(rtl88ee_driver);

Annotation

• Immediate include surface: `../wifi.h`, `../core.h`, `../pci.h`, `reg.h`, `def.h`, `phy.h`, `dm.h`, `hw.h`.
• Detected declarations: `function rtl88e_init_aspm_vars`, `function rtl88e_init_sw_vars`, `function rtl88e_deinit_sw_vars`, `function rtl88e_get_btc_status`.
• 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.