regmap_add_irq_chip(9)

📦 version 7.3.1, in nixpkgs unstable

✨ regmap_add_irq_chip(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for regmap_add_irq_chip — literally the function that gives you standard regmap IRQ controller handling 🎀 like it just handles it for you, no cap.

🌸 SYNOPSIS 🌸

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

it's giving six-argument main character energy 💅

🦋 ARGUMENTS 🦋

  • map — the regmap for the device, aka the whole vibe of what you're working with 🫶
  • irq — the IRQ that the device uses to signal interrupts, like its little "hey!! something happened!!" ping 😭
  • irq_flags — the IRQF_ flags you wanna use for the primary interrupt ⭐
  • irq_base — allocate at a specific IRQ number only if irq_base > 0, iykyk 🌈
  • chip — the configuration for the interrupt controller 👑
  • data — runtime data structure for the controller, and it gets allocated on success — so yes, you get a little gift on the way out 🎁

💜 DESCRIPTION 💜

Returns 0 on success or an errno on failure. periodt. 🔥

This is the same as regmap_add_irq_chip_fwnode, except that the firmware node of the regmap is used. like, the only difference fr fr — everything else ate 💅

heads up bestie: check that return value!! 0 means slay, an errno means not slay 🙈

🌟 SEE ALSO 🌟

and that's the whole page bestie!! this one lives at ./drivers/base/regmap, dated October 2026, and it's filed under regmap_add_irq_chip(9) — go forth and register those IRQ chips, you absolute legend 🧚💜✨

📦 where this page comes from