regmap_irq_get_virq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… regmap_irq_get_virq(9) β€” the kernel API manual, bestie edition

okay so you're looking at regmap_irq_get_virq(9), and honestly? it's a little one but it's a useful little one. it's the "hey kernel, what's the virtual IRQ for this chip interrupt" girlie. let's get into it πŸŽ€


✨ NAME ✨

regmap_irq_get_virq β€” map an interrupt on a chip to a virtual IRQ πŸ¦‹

like, you got a physical-ish interrupt chilling on a chip, and you want the virtual IRQ number that goes with it. that's the whole gig. periodt.


✨ SYNOPSIS ✨

int regmap_irq_get_virq (struct regmap_irq_chip_data *data , int irq );

that's it. that's the function. two args, one int coming back at you. πŸ’–


✨ ARGUMENTS ✨

  • data β€” the regmap irq controller you're operating on, bestie. this is the chip data struct you're poking at. 🫢
  • irq β€” the index of the interrupt you're requesting, in the chip IRQs. so like, it's an index into the chip's IRQ list, not some rando number, iykyk. πŸ”₯

✨ DESCRIPTION ✨

so what's it for? it's useful for drivers to request their own IRQs. that's literally the description. short and iconic. your driver wants its own IRQ, this is the hookup. no cap. ⭐


🌈 SEE ALSO 🌈

the whole regmap-irq friend group, basically. go say hi to all of them πŸ’…


and that's the tea, babe πŸ“ β€” this page lives in ./drivers/base/regmap and it's dated October 2026, so jot that down in your notes app. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from