arch/sh/drivers/push-switch.c

File Facts

System

Linux kernel

Corpus path

arch/sh/drivers/push-switch.c

Extension

.c

Size

3012 bytes

Lines

136

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/slab.h
• linux/module.h
• linux/interrupt.h
• linux/platform_device.h
• asm/push-switch.h

Detected Declarations

• function Copyright
• function switch_timer
• function switch_work_handler
• function switch_drv_probe
• function switch_drv_remove
• function switch_init
• function switch_exit
• module init switch_init

Annotated Snippet

module_init(switch_init);
module_exit(switch_exit);

MODULE_VERSION(DRV_VERSION);
MODULE_AUTHOR("Paul Mundt");
MODULE_DESCRIPTION("Generic push-switch framework");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/init.h`, `linux/slab.h`, `linux/module.h`, `linux/interrupt.h`, `linux/platform_device.h`, `asm/push-switch.h`.
• Detected declarations: `function Copyright`, `function switch_timer`, `function switch_work_handler`, `function switch_drv_probe`, `function switch_drv_remove`, `function switch_init`, `function switch_exit`, `module init switch_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.