arch/mips/include/asm/mach-cobalt/irq.h
Source file repositories/reference/linux-study-clean/arch/mips/include/asm/mach-cobalt/irq.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/include/asm/mach-cobalt/irq.h- Extension
.h- Size
- 1463 bytes
- Lines
- 58
- Domain
- Architecture Layer
- Bucket
- arch/mips
- 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.
Dependency Surface
asm/irq_gt641xx.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef _ASM_COBALT_IRQ_H
#define _ASM_COBALT_IRQ_H
/*
* i8259 interrupts used on Cobalt:
*
* 8 - RTC
* 9 - PCI slot
* 14 - IDE0
* 15 - IDE1(no connector on board)
*/
#define I8259A_IRQ_BASE 0
#define PCISLOT_IRQ (I8259A_IRQ_BASE + 9)
/*
* CPU interrupts used on Cobalt:
*
* 0 - Software interrupt 0 (unused)
* 1 - Software interrupt 0 (unused)
* 2 - cascade GT64111
* 3 - ethernet or SCSI host controller
* 4 - ethernet
* 5 - 16550 UART
* 6 - cascade i8259
* 7 - CP0 counter
*/
#define MIPS_CPU_IRQ_BASE 16
#define GT641XX_CASCADE_IRQ (MIPS_CPU_IRQ_BASE + 2)
#define RAQ2_SCSI_IRQ (MIPS_CPU_IRQ_BASE + 3)
#define ETH0_IRQ (MIPS_CPU_IRQ_BASE + 3)
#define QUBE1_ETH0_IRQ (MIPS_CPU_IRQ_BASE + 4)
#define ETH1_IRQ (MIPS_CPU_IRQ_BASE + 4)
#define SERIAL_IRQ (MIPS_CPU_IRQ_BASE + 5)
#define SCSI_IRQ (MIPS_CPU_IRQ_BASE + 5)
#define I8259_CASCADE_IRQ (MIPS_CPU_IRQ_BASE + 6)
#define GT641XX_IRQ_BASE 24
#include <asm/irq_gt641xx.h>
#define NR_IRQS (GT641XX_PCI_INT3_IRQ + 1)
#endif /* _ASM_COBALT_IRQ_H */
Annotation
- Immediate include surface: `asm/irq_gt641xx.h`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.