arch/arm/mach-s3c/irq-pm-s3c64xx.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-s3c/irq-pm-s3c64xx.c

Extension

.c

Size

3194 bytes

Lines

124

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/kernel.h
• linux/syscore_ops.h
• linux/interrupt.h
• linux/serial_core.h
• linux/serial_s3c.h
• linux/irq.h
• linux/io.h
• linux/of.h
• map.h
• regs-gpio.h
• cpu.h
• pm.h

Detected Declarations

• function s3c64xx_irq_pm_suspend
• function s3c64xx_irq_pm_resume
• function s3c64xx_syscore_init
• module init s3c64xx_syscore_init

Annotated Snippet

core_initcall(s3c64xx_syscore_init);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/syscore_ops.h`, `linux/interrupt.h`, `linux/serial_core.h`, `linux/serial_s3c.h`, `linux/irq.h`, `linux/io.h`, `linux/of.h`.
• Detected declarations: `function s3c64xx_irq_pm_suspend`, `function s3c64xx_irq_pm_resume`, `function s3c64xx_syscore_init`, `module init s3c64xx_syscore_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.