arch/loongarch/power/platform.c
Source file repositories/reference/linux-study-clean/arch/loongarch/power/platform.c
File Facts
- System
- Linux kernel
- Corpus path
arch/loongarch/power/platform.c- Extension
.c- Size
- 1902 bytes
- Lines
- 85
- Domain
- Architecture Layer
- Bucket
- arch/loongarch
- 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/acpi.hlinux/platform_device.hasm/bootinfo.hasm/loongson.h
Detected Declarations
function Copyrightfunction enable_pci_wakeupfunction loongson_cpufreq_initfunction default_suspend_addrfunction loongson3_acpi_suspend_initmodule init loongson3_acpi_suspend_init
Annotated Snippet
device_initcall(loongson3_acpi_suspend_init);
Annotation
- Immediate include surface: `linux/acpi.h`, `linux/platform_device.h`, `asm/bootinfo.h`, `asm/loongson.h`.
- Detected declarations: `function Copyright`, `function enable_pci_wakeup`, `function loongson_cpufreq_init`, `function default_suspend_addr`, `function loongson3_acpi_suspend_init`, `module init loongson3_acpi_suspend_init`.
- Atlas domain: Architecture Layer / arch/loongarch.
- 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.