drivers/platform/x86/asus-nb-wmi.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/asus-nb-wmi.c

Extension

.c

Size

20461 bytes

Lines

720

Domain

Driver Families

Bucket

drivers/platform

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/backlight.h
• linux/kernel.h
• linux/module.h
• linux/init.h
• linux/input.h
• linux/input/sparse-keymap.h
• linux/dmi.h
• linux/i8042.h
• acpi/video.h
• asus-wmi.h

Detected Declarations

• function asus_i8042_filter
• function dmi_matched
• function asus_nb_wmi_quirks
• function asus_nb_wmi_key_filter
• function asus_nb_wmi_init
• function asus_nb_wmi_exit
• module init asus_nb_wmi_init

Annotated Snippet

module_init(asus_nb_wmi_init);
module_exit(asus_nb_wmi_exit);

Annotation

• Immediate include surface: `linux/backlight.h`, `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/input.h`, `linux/input/sparse-keymap.h`, `linux/dmi.h`, `linux/i8042.h`.
• Detected declarations: `function asus_i8042_filter`, `function dmi_matched`, `function asus_nb_wmi_quirks`, `function asus_nb_wmi_key_filter`, `function asus_nb_wmi_init`, `function asus_nb_wmi_exit`, `module init asus_nb_wmi_init`.
• Atlas domain: Driver Families / drivers/platform.
• 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.