include/linux/soc/samsung/exynos-pmu.h
Source file repositories/reference/linux-study-clean/include/linux/soc/samsung/exynos-pmu.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/soc/samsung/exynos-pmu.h- Extension
.h- Size
- 875 bytes
- Lines
- 41
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
struct regmapstruct device_nodeenum sys_powerdown
Annotated Snippet
#ifndef __LINUX_SOC_EXYNOS_PMU_H
#define __LINUX_SOC_EXYNOS_PMU_H
struct regmap;
struct device_node;
enum sys_powerdown {
SYS_AFTR,
SYS_LPA,
SYS_SLEEP,
NUM_SYS_POWERDOWN,
};
extern void exynos_sys_powerdown_conf(enum sys_powerdown mode);
#ifdef CONFIG_EXYNOS_PMU
struct regmap *exynos_get_pmu_regmap(void);
struct regmap *exynos_get_pmu_regmap_by_phandle(struct device_node *np,
const char *propname);
#else
static inline struct regmap *exynos_get_pmu_regmap(void)
{
return ERR_PTR(-ENODEV);
}
static inline struct regmap *exynos_get_pmu_regmap_by_phandle(struct device_node *np,
const char *propname)
{
return ERR_PTR(-ENODEV);
}
#endif
#endif /* __LINUX_SOC_EXYNOS_PMU_H */
Annotation
- Detected declarations: `struct regmap`, `struct device_node`, `enum sys_powerdown`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.