arch/arm/mach-s3c/wakeup-mask.c
Source file repositories/reference/linux-study-clean/arch/arm/mach-s3c/wakeup-mask.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-s3c/wakeup-mask.c- Extension
.c- Size
- 906 bytes
- Lines
- 43
- 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
linux/kernel.hlinux/spinlock.hlinux/device.hlinux/types.hlinux/irq.hlinux/io.hwakeup-mask.hpm.h
Detected Declarations
function samsung_sync_wakemask
Annotated Snippet
if (mask->irq == NO_WAKEUP_IRQ) {
val |= mask->bit;
continue;
}
data = irq_get_irq_data(mask->irq);
/* bit of a liberty to read this directly from irq_data. */
if (irqd_is_wakeup_set(data))
val &= ~mask->bit;
else
val |= mask->bit;
}
printk(KERN_INFO "wakemask %08x => %08x\n", __raw_readl(reg), val);
__raw_writel(val, reg);
}
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/spinlock.h`, `linux/device.h`, `linux/types.h`, `linux/irq.h`, `linux/io.h`, `wakeup-mask.h`, `pm.h`.
- Detected declarations: `function samsung_sync_wakemask`.
- 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.