drivers/leds/trigger/ledtrig-camera.c

File Facts

System

Linux kernel

Corpus path

drivers/leds/trigger/ledtrig-camera.c

Extension

.c

Size

1226 bytes

Lines

54

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.

Dependency Surface

• linux/module.h
• linux/kernel.h
• linux/init.h
• linux/leds.h

Detected Declarations

• function ledtrig_flash_ctrl
• function ledtrig_torch_ctrl
• function ledtrig_camera_init
• function ledtrig_camera_exit
• module init ledtrig_camera_init
• export ledtrig_flash_ctrl
• export ledtrig_torch_ctrl

Annotated Snippet

module_init(ledtrig_camera_init);

static void __exit ledtrig_camera_exit(void)
{
	led_trigger_unregister_simple(ledtrig_torch);
	led_trigger_unregister_simple(ledtrig_flash);
}
module_exit(ledtrig_camera_exit);

MODULE_DESCRIPTION("LED Trigger for Camera Flash/Torch Control");
MODULE_AUTHOR("Milo Kim");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/init.h`, `linux/leds.h`.
• Detected declarations: `function ledtrig_flash_ctrl`, `function ledtrig_torch_ctrl`, `function ledtrig_camera_init`, `function ledtrig_camera_exit`, `module init ledtrig_camera_init`, `export ledtrig_flash_ctrl`, `export ledtrig_torch_ctrl`.
• 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.