STRUCT DPRC_IRQ_CFG(9)

💖 NAME 💖

okay bestie, meet struct dprc_irq_cfg from the Kernel API Manual — that’s struct dprc_irq_cfg(9), iykyk — and it is literally the IRQ configuration struct. iconic behavior only. ✨

✨ SYNOPSIS ✨

the whole struct is giving “short but powerful,” and it looks exactly like this:

struct dprc_irq_cfg {
    phys_addr_t paddr;
    u32 val;
    int irq_num;
 };

🫶 Members 🫶

• paddr — a phys_addr_t, bestie: the address that must be written to signal a message-based interrupt. no cap, that’s the whole job. ✨
• val — a u32, aka the value to write into irq_addr address. periodt. 💅
• irq_num — an int, and it’s a user defined number associated with this IRQ. cute, customizable, on brand. 🎀

🌈 SEE ALSO 🌈

the kernel file in the mix is ./drivers/bus/fsl-mc/fsl-mc-private.h, and the whole squad pulls up like:

• struct dprc_attributes(9)
• enum dprc_region_type(9)
• struct dprc_region_desc(9)
• struct dprc_endpoint(9)
• struct fsl_mc_resource_pool(9)
• struct fsl_mc_uapi(9)
• struct fsl_mc_bus(9)

signed off from ./drivers/bus/fsl-mc, dated October 2026, and yes the page is literally struct dprc_irq_cfg(9) — bye bestie, slay responsibly! 💖🦋