drivers/acpi/arm64/cpuidle.c
Source file repositories/reference/linux-study-clean/drivers/acpi/arm64/cpuidle.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/acpi/arm64/cpuidle.c- Extension
.c- Size
- 1583 bytes
- Lines
- 67
- Domain
- Driver Families
- Bucket
- drivers/acpi
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/acpi.hlinux/cpuidle.hlinux/cpu_pm.hlinux/psci.hacpi/processor.h
Detected Declarations
function Copyrightfunction acpi_processor_ffh_lpi_probefunction acpi_processor_ffh_lpi_enter
Annotated Snippet
if (!psci_power_state_is_valid(state)) {
pr_warn("Invalid PSCI power state %#x\n", state);
return -EINVAL;
}
}
return 0;
}
int acpi_processor_ffh_lpi_probe(unsigned int cpu)
{
return psci_acpi_cpu_init_idle(cpu);
}
__cpuidle int acpi_processor_ffh_lpi_enter(struct acpi_lpi_state *lpi)
{
u32 state = lpi->address;
if (ARM64_LPI_IS_RETENTION_STATE(lpi->arch_flags))
return CPU_PM_CPU_IDLE_ENTER_RETENTION_PARAM_RCU(psci_cpu_suspend_enter,
lpi->index, state);
else
return CPU_PM_CPU_IDLE_ENTER_PARAM_RCU(psci_cpu_suspend_enter,
lpi->index, state);
}
Annotation
- Immediate include surface: `linux/acpi.h`, `linux/cpuidle.h`, `linux/cpu_pm.h`, `linux/psci.h`, `acpi/processor.h`.
- Detected declarations: `function Copyright`, `function acpi_processor_ffh_lpi_probe`, `function acpi_processor_ffh_lpi_enter`.
- Atlas domain: Driver Families / drivers/acpi.
- Implementation status: source 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.