arch/arm/mach-pxa/smemc.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-pxa/smemc.c

Extension

.c

Size

2067 bytes

Lines

86

Domain

Architecture Layer

Bucket

arch/arm

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/module.h
• linux/kernel.h
• linux/init.h
• linux/io.h
• linux/syscore_ops.h
• linux/soc/pxa/cpu.h
• smemc.h
• linux/soc/pxa/smemc.h

Detected Declarations

• function pxa3xx_smemc_suspend
• function pxa3xx_smemc_resume
• function smemc_init
• function pxa3xx_smemc_get_memclkdiv
• module init smemc_init

Annotated Snippet

subsys_initcall(smemc_init);
#endif

static const unsigned int df_clkdiv[4] = { 1, 2, 4, 1 };
unsigned int pxa3xx_smemc_get_memclkdiv(void)
{
	unsigned long memclkcfg = __raw_readl(MEMCLKCFG);

	return	df_clkdiv[(memclkcfg >> 16) & 0x3];
}

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/init.h`, `linux/io.h`, `linux/syscore_ops.h`, `linux/soc/pxa/cpu.h`, `smemc.h`, `linux/soc/pxa/smemc.h`.
• Detected declarations: `function pxa3xx_smemc_suspend`, `function pxa3xx_smemc_resume`, `function smemc_init`, `function pxa3xx_smemc_get_memclkdiv`, `module init smemc_init`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.