arch/arm/mach-imx/pm-imx25.c
Source file repositories/reference/linux-study-clean/arch/arm/mach-imx/pm-imx25.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-imx/pm-imx25.c- Extension
.c- Size
- 598 bytes
- Lines
- 36
- Domain
- Architecture Layer
- Bucket
- arch/arm
- Inferred role
- Architecture Layer: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/kernel.hlinux/suspend.hlinux/io.hcommon.h
Detected Declarations
function imx25_suspend_enterfunction imx25_pm_init
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* Copyright 2016 NXP Semiconductors
*/
#include <linux/kernel.h>
#include <linux/suspend.h>
#include <linux/io.h>
#include "common.h"
static int imx25_suspend_enter(suspend_state_t state)
{
if (!IS_ENABLED(CONFIG_PM))
return 0;
switch (state) {
case PM_SUSPEND_MEM:
cpu_do_idle();
break;
default:
return -EINVAL;
}
return 0;
}
static const struct platform_suspend_ops imx25_suspend_ops = {
.enter = imx25_suspend_enter,
.valid = suspend_valid_only_mem,
};
void __init imx25_pm_init(void)
{
suspend_set_ops(&imx25_suspend_ops);
}
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/suspend.h`, `linux/io.h`, `common.h`.
- Detected declarations: `function imx25_suspend_enter`, `function imx25_pm_init`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.