drivers/leds/leds-locomo.c

File Facts

System

Linux kernel

Corpus path

drivers/leds/leds-locomo.c

Extension

.c

Size

1961 bytes

Lines

83

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/module.h
• linux/device.h
• linux/leds.h
• asm/hardware/locomo.h

Detected Declarations

• function Copyright
• function locomoled_brightness_set0
• function locomoled_brightness_set1
• function locomoled_probe
• function locomoled_init
• module init locomoled_init

Annotated Snippet

module_init(locomoled_init);

MODULE_AUTHOR("John Lenz <lenz@cs.wisc.edu>");
MODULE_DESCRIPTION("Locomo LED driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/module.h`, `linux/device.h`, `linux/leds.h`, `asm/hardware/locomo.h`.
• Detected declarations: `function Copyright`, `function locomoled_brightness_set0`, `function locomoled_brightness_set1`, `function locomoled_probe`, `function locomoled_init`, `module init locomoled_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.