arch/powerpc/platforms/pseries/event_sources.c
Source file repositories/reference/linux-study-clean/arch/powerpc/platforms/pseries/event_sources.c
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/platforms/pseries/event_sources.c- Extension
.c- Size
- 676 bytes
- Lines
- 31
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- 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.
- 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/interrupt.hlinux/of_irq.hpseries.h
Detected Declarations
function Copyright
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-or-later
/*
* Copyright (C) 2001 Dave Engebretsen IBM Corporation
*/
#include <linux/interrupt.h>
#include <linux/of_irq.h>
#include "pseries.h"
void __init request_event_sources_irqs(struct device_node *np,
irq_handler_t handler,
const char *name)
{
int i, virq, rc;
for (i = 0; i < 16; i++) {
virq = of_irq_get(np, i);
if (virq < 0)
return;
if (WARN(!virq, "event-sources: Unable to allocate "
"interrupt number for %pOF\n", np))
continue;
rc = request_irq(virq, handler, 0, name, NULL);
if (WARN(rc, "event-sources: Unable to request interrupt %d for %pOF\n",
virq, np))
return;
}
}
Annotation
- Immediate include surface: `linux/interrupt.h`, `linux/of_irq.h`, `pseries.h`.
- Detected declarations: `function Copyright`.
- Atlas domain: Architecture Layer / arch/powerpc.
- Implementation status: source 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.