drivers/leds/led-class.c

File Facts

System

Linux kernel

Corpus path

drivers/leds/led-class.c

Extension

.c

Size

18293 bytes

Lines

732

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/ctype.h
• linux/device.h
• linux/err.h
• linux/init.h
• linux/kernel.h
• linux/leds.h
• linux/list.h
• linux/module.h
• linux/property.h
• linux/slab.h
• linux/spinlock.h
• linux/timer.h
• uapi/linux/uleds.h
• linux/of.h
• leds.h

Detected Declarations

• function led_trigger_is_hw_controlled
• function brightness_show
• function brightness_store
• function max_brightness_show
• function brightness_hw_changed_show
• function led_add_brightness_hw_changed
• function led_remove_brightness_hw_changed
• function led_classdev_notify_brightness_hw_changed
• function led_add_brightness_hw_changed
• function led_remove_brightness_hw_changed
• function led_classdev_resume
• function led_suspend
• function led_resume
• function fwnode_led_get
• function led_put
• function devm_led_release
• function devm_of_led_get
• function led_get
• function devm_led_get
• function led_add_lookup
• function led_remove_lookup
• function devm_of_led_get_optional
• function led_classdev_next_name
• function led_classdev_register_ext
• function led_classdev_unregister
• function devm_led_classdev_release
• function devm_led_classdev_register_ext
• function devm_led_classdev_match
• function devm_led_classdev_unregister
• function leds_init
• function leds_exit
• module init leds_init
• export led_classdev_notify_brightness_hw_changed
• export led_classdev_suspend
• export led_classdev_resume
• export led_put
• export devm_of_led_get
• export led_get
• export devm_led_get
• export led_add_lookup
• export led_remove_lookup
• export devm_of_led_get_optional
• export led_classdev_register_ext
• export led_classdev_unregister
• export devm_led_classdev_register_ext
• export devm_led_classdev_unregister

Annotated Snippet

subsys_initcall(leds_init);
module_exit(leds_exit);

MODULE_AUTHOR("John Lenz, Richard Purdie");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("LED Class Interface");

Annotation

• Immediate include surface: `linux/ctype.h`, `linux/device.h`, `linux/err.h`, `linux/init.h`, `linux/kernel.h`, `linux/leds.h`, `linux/list.h`, `linux/module.h`.
• Detected declarations: `function led_trigger_is_hw_controlled`, `function brightness_show`, `function brightness_store`, `function max_brightness_show`, `function brightness_hw_changed_show`, `function led_add_brightness_hw_changed`, `function led_remove_brightness_hw_changed`, `function led_classdev_notify_brightness_hw_changed`, `function led_add_brightness_hw_changed`, `function led_remove_brightness_hw_changed`.
• Atlas domain: Driver Families / drivers/leds.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.