arch/sh/boards/mach-hp6xx/hp6xx_apm.c

File Facts

System

Linux kernel

Corpus path

arch/sh/boards/mach-hp6xx/hp6xx_apm.c

Extension

.c

Size

2690 bytes

Lines

110

Domain

Architecture Layer

Bucket

arch/sh

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/interrupt.h
• linux/apm-emulation.h
• linux/io.h
• asm/adc.h
• mach/hp6xx.h

Detected Declarations

• function hp6x0_apm_get_power_status
• function hp6x0_apm_interrupt
• function hp6x0_apm_init
• function hp6x0_apm_exit
• module init hp6x0_apm_init

Annotated Snippet

module_init(hp6x0_apm_init);
module_exit(hp6x0_apm_exit);

MODULE_AUTHOR("Adriy Skulysh");
MODULE_DESCRIPTION("hp6xx Advanced Power Management");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/init.h`, `linux/interrupt.h`, `linux/apm-emulation.h`, `linux/io.h`, `asm/adc.h`, `mach/hp6xx.h`.
• Detected declarations: `function hp6x0_apm_get_power_status`, `function hp6x0_apm_interrupt`, `function hp6x0_apm_init`, `function hp6x0_apm_exit`, `module init hp6x0_apm_init`.
• Atlas domain: Architecture Layer / arch/sh.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.