drivers/irqchip/irq-versatile-fpga.c
Source file repositories/reference/linux-study-clean/drivers/irqchip/irq-versatile-fpga.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/irqchip/irq-versatile-fpga.c- Extension
.c- Size
- 6231 bytes
- Lines
- 246
- Domain
- Driver Families
- Bucket
- drivers/irqchip
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bitops.hlinux/irq.hlinux/io.hlinux/irqchip.hlinux/irqchip/chained_irq.hlinux/irqdomain.hlinux/module.hlinux/of.hlinux/of_address.hlinux/of_irq.hlinux/seq_file.hasm/exception.hasm/mach/irq.h
Detected Declarations
struct fpga_irq_datafunction fpga_irq_maskfunction fpga_irq_unmaskfunction fpga_irq_print_chipfunction fpga_irq_handlefunction handle_one_fpgafunction fpga_handle_irqfunction fpga_irqdomain_mapfunction fpga_irq_initfunction fpga_irq_of_init
Annotated Snippet
struct fpga_irq_data {
void __iomem *base;
u32 valid;
struct irq_domain *domain;
u8 used_irqs;
};
/* we cannot allocate memory when the controllers are initially registered */
static struct fpga_irq_data fpga_irq_devices[CONFIG_VERSATILE_FPGA_IRQ_NR];
static int fpga_irq_id;
static void fpga_irq_mask(struct irq_data *d)
{
struct fpga_irq_data *f = irq_data_get_irq_chip_data(d);
u32 mask = 1 << d->hwirq;
writel(mask, f->base + IRQ_ENABLE_CLEAR);
}
static void fpga_irq_unmask(struct irq_data *d)
{
struct fpga_irq_data *f = irq_data_get_irq_chip_data(d);
u32 mask = 1 << d->hwirq;
writel(mask, f->base + IRQ_ENABLE_SET);
}
static void fpga_irq_print_chip(struct irq_data *d, struct seq_file *p)
{
struct fpga_irq_data *f = irq_data_get_irq_chip_data(d);
seq_puts(p, irq_domain_get_of_node(f->domain)->name);
}
static const struct irq_chip fpga_chip = {
.irq_ack = fpga_irq_mask,
.irq_mask = fpga_irq_mask,
.irq_unmask = fpga_irq_unmask,
.irq_print_chip = fpga_irq_print_chip,
};
static void fpga_irq_handle(struct irq_desc *desc)
{
struct irq_chip *chip = irq_desc_get_chip(desc);
struct fpga_irq_data *f = irq_desc_get_handler_data(desc);
u32 status;
chained_irq_enter(chip, desc);
status = readl(f->base + IRQ_STATUS);
if (status == 0) {
handle_bad_irq(desc);
goto out;
}
do {
unsigned int irq = ffs(status) - 1;
status &= ~(1 << irq);
generic_handle_domain_irq(f->domain, irq);
} while (status);
out:
chained_irq_exit(chip, desc);
}
/*
* Handle each interrupt in a single FPGA IRQ controller. Returns non-zero
* if we've handled at least one interrupt. This does a single read of the
* status register and handles all interrupts in order from LSB first.
*/
static int handle_one_fpga(struct fpga_irq_data *f, struct pt_regs *regs)
{
int handled = 0;
int irq;
u32 status;
while ((status = readl(f->base + IRQ_STATUS))) {
irq = ffs(status) - 1;
generic_handle_domain_irq(f->domain, irq);
handled = 1;
}
return handled;
}
/*
* Keep iterating over all registered FPGA IRQ controllers until there are
* no pending interrupts.
*/
Annotation
- Immediate include surface: `linux/bitops.h`, `linux/irq.h`, `linux/io.h`, `linux/irqchip.h`, `linux/irqchip/chained_irq.h`, `linux/irqdomain.h`, `linux/module.h`, `linux/of.h`.
- Detected declarations: `struct fpga_irq_data`, `function fpga_irq_mask`, `function fpga_irq_unmask`, `function fpga_irq_print_chip`, `function fpga_irq_handle`, `function handle_one_fpga`, `function fpga_handle_irq`, `function fpga_irqdomain_map`, `function fpga_irq_init`, `function fpga_irq_of_init`.
- Atlas domain: Driver Families / drivers/irqchip.
- 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.