drivers/leds/leds-wrap.c

File Facts

System

Linux kernel

Corpus path

drivers/leds/leds-wrap.c

Extension

.c

Size

2787 bytes

Lines

131

Domain

Driver Families

Bucket

drivers/leds

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/kernel.h
• linux/init.h
• linux/platform_device.h
• linux/leds.h
• linux/err.h
• linux/io.h
• linux/scx200_gpio.h
• linux/module.h

Detected Declarations

• function wrap_power_led_set
• function wrap_error_led_set
• function wrap_extra_led_set
• function wrap_led_probe
• function wrap_led_init
• function wrap_led_exit
• module init wrap_led_init

Annotated Snippet

module_init(wrap_led_init);
module_exit(wrap_led_exit);

MODULE_AUTHOR("Kristian Kielhofner <kris@krisk.org>");
MODULE_DESCRIPTION("PCEngines WRAP LED driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/platform_device.h`, `linux/leds.h`, `linux/err.h`, `linux/io.h`, `linux/scx200_gpio.h`, `linux/module.h`.
• Detected declarations: `function wrap_power_led_set`, `function wrap_error_led_set`, `function wrap_extra_led_set`, `function wrap_led_probe`, `function wrap_led_init`, `function wrap_led_exit`, `module init wrap_led_init`.
• Atlas domain: Driver Families / drivers/leds.
• 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.