include/linux/irq_sim.h
Source file repositories/reference/linux-study-clean/include/linux/irq_sim.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/irq_sim.h- Extension
.h- Size
- 1379 bytes
- Lines
- 44
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/device.hlinux/fwnode.hlinux/irqdomain.h
Detected Declarations
struct irq_sim_ops
Annotated Snippet
struct irq_sim_ops {
int (*irq_sim_irq_requested)(struct irq_domain *domain,
irq_hw_number_t hwirq, void *data);
void (*irq_sim_irq_released)(struct irq_domain *domain,
irq_hw_number_t hwirq, void *data);
};
struct irq_domain *irq_domain_create_sim(struct fwnode_handle *fwnode,
unsigned int num_irqs);
struct irq_domain *devm_irq_domain_create_sim(struct device *dev,
struct fwnode_handle *fwnode,
unsigned int num_irqs);
struct irq_domain *irq_domain_create_sim_full(struct fwnode_handle *fwnode,
unsigned int num_irqs,
const struct irq_sim_ops *ops,
void *data);
struct irq_domain *
devm_irq_domain_create_sim_full(struct device *dev,
struct fwnode_handle *fwnode,
unsigned int num_irqs,
const struct irq_sim_ops *ops,
void *data);
void irq_domain_remove_sim(struct irq_domain *domain);
#endif /* _LINUX_IRQ_SIM_H */
Annotation
- Immediate include surface: `linux/device.h`, `linux/fwnode.h`, `linux/irqdomain.h`.
- Detected declarations: `struct irq_sim_ops`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.