arch/sh/boards/mach-dreamcast/irq.c
Source file repositories/reference/linux-study-clean/arch/sh/boards/mach-dreamcast/irq.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/boards/mach-dreamcast/irq.c- Extension
.c- Size
- 4391 bytes
- Lines
- 156
- Domain
- Architecture Layer
- Bucket
- arch/sh
- 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/irq.hlinux/io.hlinux/export.hlinux/err.hmach/sysasic.h
Detected Declarations
function disable_systemasic_irqfunction enable_systemasic_irqfunction mask_ack_systemasic_irqfunction systemasic_irq_demuxfunction systemasic_irq_init
Annotated Snippet
if (status & bit) {
irq = HW_EVENT_IRQ_BASE + j + (level << 5);
return irq;
}
}
/* Not reached */
return irq;
}
void systemasic_irq_init(void)
{
int irq_base, i;
irq_base = irq_alloc_descs(HW_EVENT_IRQ_BASE, HW_EVENT_IRQ_BASE,
HW_EVENT_IRQ_MAX - HW_EVENT_IRQ_BASE, -1);
if (IS_ERR_VALUE(irq_base)) {
pr_err("%s: failed hooking irqs\n", __func__);
return;
}
for (i = HW_EVENT_IRQ_BASE; i < HW_EVENT_IRQ_MAX; i++)
irq_set_chip_and_handler(i, &systemasic_int, handle_level_irq);
}
Annotation
- Immediate include surface: `linux/irq.h`, `linux/io.h`, `linux/export.h`, `linux/err.h`, `mach/sysasic.h`.
- Detected declarations: `function disable_systemasic_irq`, `function enable_systemasic_irq`, `function mask_ack_systemasic_irq`, `function systemasic_irq_demux`, `function systemasic_irq_init`.
- Atlas domain: Architecture Layer / arch/sh.
- 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.