regmap_add_irq_chip_fwnode(9)

🌸 NAME 🌸

regmap_add_irq_chip_fwnode — use standard regmap IRQ controller handling. This page is from the Kernel API Manual, and it's literally the regmap_add_irq_chip_fwnode(9) glow-up: fwnode edition. 💅✨

✨ SYNOPSIS ✨

int regmap_add_irq_chip_fwnode (struct fwnode_handle *fwnode , struct
regmap *map , int irq , int irq_flags , int irq_base , const struct
regmap_irq_chip *chip , struct regmap_irq_chip_data **data );

💖 ARGUMENTS 💖

• fwnode — the firmware node where the IRQ domain should be added to. that's the destination, bestie 🎀
• map — the regmap for the device. the device's regmap, iconic.
• irq — the IRQ the device uses to signal interrupts. the interrupt signal's whole vibe.
• irq_flags — the IRQF_ flags to use for the primary interrupt. flags for the primary interrupt — noted, bestie 🫶
• irq_base — allocate at a specific IRQ number if irq_base > 0. conditional cutie.
• chip — configuration for the interrupt controller. the controller config, slay.
• data — runtime data structure for the controller, allocated on success. allocated on success — love that for you.

🌈 DESCRIPTION 🌈

Okay so, the return value: 0 on success or an errno on failure. That's it, that's the rule. 🌈

For this to be efficient, the chip really should use a register cache. no cap, it matters. And the chip driver is responsible for restoring the register values used by the IRQ controller over suspend and resume. driver's job, bestie — don't forget it. 🫶

🦋 SEE ALSO 🦋

• Kernel file ./drivers/base/regmap/regmap-irq.c
• regmap_irq_get_irq_reg_linear(9)
• regmap_irq_set_type_config_simple(9)
• regmap_add_irq_chip(9)
• regmap_del_irq_chip(9)
• devm_regmap_add_irq_chip_fwnode(9)
• devm_regmap_add_irq_chip(9)
• devm_regmap_del_irq_chip(9)
• regmap_irq_chip_get_base(9)
• regmap_irq_get_virq(9)
• regmap_irq_get_domain(9)

source/version: ./drivers/base/regmap · date: October 2026 · page: regmap_add_irq_chip_fwnode(9) — bye bestie, go make those IRQs iconic 💅💖✨