arch/sparc/kernel/led.c

File Facts

System

Linux kernel

Corpus path

arch/sparc/kernel/led.c

Extension

.c

Size

3264 bytes

Lines

147

Domain

Architecture Layer

Bucket

arch/sparc

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• 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/module.h
• linux/init.h
• linux/proc_fs.h
• linux/seq_file.h
• linux/slab.h
• linux/string.h
• linux/jiffies.h
• linux/timer.h
• linux/uaccess.h
• linux/sched/loadavg.h
• asm/auxio.h

Detected Declarations

• function led_toggle
• function led_blink
• function led_proc_show
• function led_proc_open
• function led_proc_write
• function led_init
• function led_exit
• module init led_init

Annotated Snippet

module_init(led_init);
module_exit(led_exit);

MODULE_AUTHOR("Lars Kotthoff <metalhead@metalhead.ws>");
MODULE_DESCRIPTION("Provides control of the front LED on SPARC systems.");
MODULE_LICENSE("GPL");
MODULE_VERSION(LED_VERSION);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/proc_fs.h`, `linux/seq_file.h`, `linux/slab.h`, `linux/string.h`, `linux/jiffies.h`.
• Detected declarations: `function led_toggle`, `function led_blink`, `function led_proc_show`, `function led_proc_open`, `function led_proc_write`, `function led_init`, `function led_exit`, `module init led_init`.
• Atlas domain: Architecture Layer / arch/sparc.
• 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.