drivers/irqchip/irq-ast2700.h
Source file repositories/reference/linux-study-clean/drivers/irqchip/irq-ast2700.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/irqchip/irq-ast2700.h- Extension
.h- Size
- 1246 bytes
- Lines
- 49
- 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/device.hlinux/irqdomain.h
Detected Declarations
struct aspeed_intc_interrupt_rangestruct aspeed_intc_interrupt_rangesstruct aspeed_intc0
Annotated Snippet
struct aspeed_intc_interrupt_range {
u32 start;
u32 count;
struct irq_fwspec upstream;
struct irq_domain *domain;
};
struct aspeed_intc_interrupt_ranges {
struct aspeed_intc_interrupt_range *ranges;
unsigned int nranges;
};
struct aspeed_intc0 {
struct device *dev;
void __iomem *base;
raw_spinlock_t intc_lock;
struct irq_domain *local;
struct device_node *parent;
struct aspeed_intc_interrupt_ranges ranges;
};
int aspeed_intc_populate_ranges(struct device *dev,
struct aspeed_intc_interrupt_ranges *ranges);
int aspeed_intc0_resolve_route(const struct irq_domain *c0domain,
size_t nc1outs,
const u32 *c1outs,
size_t nc1ranges,
const struct aspeed_intc_interrupt_range *c1ranges,
struct aspeed_intc_interrupt_range *resolved);
#endif
Annotation
- Immediate include surface: `linux/device.h`, `linux/irqdomain.h`.
- Detected declarations: `struct aspeed_intc_interrupt_range`, `struct aspeed_intc_interrupt_ranges`, `struct aspeed_intc0`.
- 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.