drivers/leds/trigger/ledtrig-panic.c

File Facts

System

Linux kernel

Corpus path

drivers/leds/trigger/ledtrig-panic.c

Extension

.c

Size

1625 bytes

Lines

69

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/kernel.h
• linux/init.h
• linux/notifier.h
• linux/panic_notifier.h
• linux/leds.h
• ../leds.h

Detected Declarations

• function led_trigger_set_panic
• function led_trigger_panic_notifier
• function led_panic_blink
• function ledtrig_panic_init
• module init ledtrig_panic_init

Annotated Snippet

device_initcall(ledtrig_panic_init);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/notifier.h`, `linux/panic_notifier.h`, `linux/leds.h`, `../leds.h`.
• Detected declarations: `function led_trigger_set_panic`, `function led_trigger_panic_notifier`, `function led_panic_blink`, `function ledtrig_panic_init`, `module init ledtrig_panic_init`.
• 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.