devm_regmap_del_irq_chip(9)

💅 devm_regmap_del_irq_chip(9) — from the Kernel API Manual, bestie

okay so picture this: you're deep in kernel-land, the devm_* family is your ride-or-die, and you need to yeet an IRQ chip the managed way. That's literally this function. Come with me 🫶

---

✨ SYNOPSIS ✨

void devm_regmap_del_irq_chip (struct device *dev , int irq , struct
regmap_irq_chip_data *data );

no cap, that's the whole signature. returns void — it's giving "I handle it, you don't gotta worry" energy 💅

---

🎀 ARGUMENTS 🎀

• dev — the Device for which the resource was allocated. like, the whole reason this is managed in the first place 🧚
• irq — the Primary IRQ for the device. yes queen, the main one, not the little baby virqs 🌸
• data — the regmap_irq_chip_data allocated by regmap_add_irq_chip. the thing you're cleaning up, bestie 😭

---

🦋 DESCRIPTION 🦋

It's a resource managed version of regmap_del_irq_chip. that's it, that's the tweet ✨

fr fr, that's the entire description — this one's short and iconic, and honestly? respect. 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/base/regmap/regmap-irq.c — the mothership, go read it 💖
• regmap_irq_get_irq_reg_linear(9)
• regmap_irq_set_type_config_simple(9)
• regmap_add_irq_chip_fwnode(9)
• regmap_add_irq_chip(9)
• regmap_del_irq_chip(9) — the un-managed sibling, the non-devm one, iykyk
• devm_regmap_add_irq_chip_fwnode(9)
• devm_regmap_add_irq_chip(9)
• regmap_irq_chip_get_base(9)
• regmap_irq_get_virq(9)
• regmap_irq_get_domain(9)

the whole regmap-irq friend group, honestly obsessed 🫶⭐

---

💀 reminder: devm_ means the cleanup is handled for you — so don't go double-freeing, bestie, that's not the vibe check you want.

---

and that's the page!! mwah 🩷

this cutie lives in ./drivers/base/regmap, dated October 2026, and answers to devm_regmap_del_irq_chip(9) — see u in the next manpage, love u, bye 🎀💜