drivers/platform/x86/tuxedo/nb04/wmi_ab.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/tuxedo/nb04/wmi_ab.c

Extension

.c

Size

31084 bytes

Lines

924

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.
• 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/dmi.h
• linux/hid.h
• linux/minmax.h
• linux/module.h
• linux/wmi.h
• wmi_util.h

Detected Declarations

• struct tux_kbl_map_entry_t
• struct tux_driver_data_t
• struct tux_hdev_driver_data_t
• function tux_ll_start
• function tux_ll_stop
• function tux_ll_close
• function handle_lamp_array_attributes_report
• function handle_lamp_attributes_request_report
• function handle_lamp_attributes_response_report
• function handle_lamp_multi_update_report
• function handle_lamp_range_update_report
• function handle_lamp_array_control_report
• function tux_ll_raw_request
• function tux_virt_lamparray_add_device
• function tux_probe
• function tux_remove
• function tuxedo_nb04_wmi_tux_init
• function tuxedo_nb04_wmi_tux_exit
• module init tuxedo_nb04_wmi_tux_init

Annotated Snippet

module_init(tuxedo_nb04_wmi_tux_init);

static void __exit tuxedo_nb04_wmi_tux_exit(void)
{
	return wmi_driver_unregister(&tuxedo_nb04_wmi_tux_driver);
}
module_exit(tuxedo_nb04_wmi_tux_exit);

MODULE_DESCRIPTION("Virtual HID LampArray interface for TUXEDO NB04 devices");
MODULE_AUTHOR("Werner Sembach <wse@tuxedocomputers.com>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/dmi.h`, `linux/hid.h`, `linux/minmax.h`, `linux/module.h`, `linux/wmi.h`, `wmi_util.h`.
• Detected declarations: `struct tux_kbl_map_entry_t`, `struct tux_driver_data_t`, `struct tux_hdev_driver_data_t`, `function tux_ll_start`, `function tux_ll_stop`, `function tux_ll_close`, `function handle_lamp_array_attributes_report`, `function handle_lamp_attributes_request_report`, `function handle_lamp_attributes_response_report`, `function handle_lamp_multi_update_report`.
• 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.