arch/arm/mach-at91/pm.h

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-at91/pm.h

Extension

.h

Size

1011 bytes

Lines

47

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

• asm/proc-fns.h
• linux/mfd/syscon/atmel-mc.h
• soc/at91/at91sam9_ddrsdr.h
• soc/at91/at91sam9_sdramc.h
• soc/at91/sama7-ddr.h
• soc/at91/sama7-sfrbu.h

Detected Declarations

• struct at91_pm_data

Annotated Snippet

struct at91_pm_data {
	void __iomem *pmc;
	void __iomem *ramc[2];
	void __iomem *ramc_phy;
	unsigned long uhp_udp_mask;
	unsigned int memctrl;
	unsigned int mode;
	void __iomem *shdwc;
	void __iomem *sfrbu;
	unsigned int standby_mode;
	unsigned int suspend_mode;
	unsigned int pmc_mckr_offset;
	unsigned int pmc_version;
	unsigned int pmc_mcks;
};
#endif

#endif

Annotation

• Immediate include surface: `asm/proc-fns.h`, `linux/mfd/syscon/atmel-mc.h`, `soc/at91/at91sam9_ddrsdr.h`, `soc/at91/at91sam9_sdramc.h`, `soc/at91/sama7-ddr.h`, `soc/at91/sama7-sfrbu.h`.
• Detected declarations: `struct at91_pm_data`.
• 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.