drivers/irqchip/irq-st.c
Source file repositories/reference/linux-study-clean/drivers/irqchip/irq-st.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/irqchip/irq-st.c- Extension
.c- Size
- 4730 bytes
- Lines
- 184
- Domain
- Driver Families
- Bucket
- drivers/irqchip
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
dt-bindings/interrupt-controller/irq-st.hlinux/err.hlinux/mfd/syscon.hlinux/of.hlinux/platform_device.hlinux/regmap.hlinux/slab.h
Detected Declarations
struct st_irq_syscfgfunction st_irq_xlatefunction st_irq_syscfg_enablefunction st_irq_syscfg_probefunction st_irq_syscfg_resumefunction st_irq_syscfg_initmodule init st_irq_syscfg_init
Annotated Snippet
core_initcall(st_irq_syscfg_init);Annotation
- Immediate include surface: `dt-bindings/interrupt-controller/irq-st.h`, `linux/err.h`, `linux/mfd/syscon.h`, `linux/of.h`, `linux/platform_device.h`, `linux/regmap.h`, `linux/slab.h`.
- Detected declarations: `struct st_irq_syscfg`, `function st_irq_xlate`, `function st_irq_syscfg_enable`, `function st_irq_syscfg_probe`, `function st_irq_syscfg_resume`, `function st_irq_syscfg_init`, `module init st_irq_syscfg_init`.
- Atlas domain: Driver Families / drivers/irqchip.
- Implementation status: integration 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.