arch/x86/platform/ts5500/ts5500.c
Source file repositories/reference/linux-study-clean/arch/x86/platform/ts5500/ts5500.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/platform/ts5500/ts5500.c- Extension
.c- Size
- 9041 bytes
- Lines
- 342
- Domain
- Architecture Layer
- Bucket
- arch/x86
- 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.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/delay.hlinux/io.hlinux/kernel.hlinux/leds.hlinux/init.hlinux/platform_data/max197.hlinux/platform_device.hlinux/slab.h
Detected Declarations
struct ts5500_sbcfunction ts5500_check_signaturefunction ts5500_detect_configfunction name_showfunction id_showfunction jumpers_showfunction ts5500_led_setfunction ts5500_led_getfunction ts5500_adc_convertfunction ts5500_initmodule init ts5500_init
Annotated Snippet
device_initcall(ts5500_init);Annotation
- Immediate include surface: `linux/delay.h`, `linux/io.h`, `linux/kernel.h`, `linux/leds.h`, `linux/init.h`, `linux/platform_data/max197.h`, `linux/platform_device.h`, `linux/slab.h`.
- Detected declarations: `struct ts5500_sbc`, `function ts5500_check_signature`, `function ts5500_detect_config`, `function name_show`, `function id_show`, `function jumpers_show`, `function ts5500_led_set`, `function ts5500_led_get`, `function ts5500_adc_convert`, `function ts5500_init`.
- Atlas domain: Architecture Layer / arch/x86.
- 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.