regulator_ir...event_simple(9)

💖 NAME 💖

okay so bestie, welcome to the Kernel API Manual entry for regulator_irq_map_event_simple — it's literally the regulator IRQ notification hook for trivial IRQs ✨ like it's the low-effort queen of IRQ mapping and honestly? she ate 🎀

---

✨ SYNOPSIS ✨

int regulator_irq_map_event_simple (int irq , struct regulator_irq_data *rid , unsigned long *dev_mask );

---

🫶 ARGUMENTS 🫶

• irq — the number of the IRQ that actually happened, yep, that's it, that's the whole vibe check 💅
• rid — the info about the event the IRQ is telling you about 👀. This function fills in the regulator_err_state->notifs and regulator_err_state->errors fields of regulator_irq_data->states as output. so it's giving "here's your data, now I'm writing into it" energy, no cap 🌸
• dev_mask — the mask that indicates which regulator originated the IRQ 🦋 iykyk

---

🌈 DESCRIPTION 🌈

So here's the tea ☕: some regulators have an IRQ with one single, well-defined purpose — meaning it always indicates exactly one event, and it's relevant to exactly one regulator device. Those lucky low-maintenance icons can use this function as their map_event callback for their regulator IRQ notification helper 😌✨

But — and this is the important part, don't @ me — for regulator_irq_map_event_simple to even be viable, you gotta register exactly one rdev and exactly one error (in the "common_errs"-field) at IRQ helper registration 🎯 like, one and one only. periodt. 💀

---

⭐ RETURN ⭐

0. that's it. that's the whole return value. iconic honestly 👑

---

🦋 SEE ALSO 🦋

• the kernel file ./drivers/regulator/irq_helpers.c 🧚
• regulator_irq_helper(9)
• regulator_irq_helper_cancel(9)

go read those next bestie, they're right there 💜

---

and that's a wrap! 🎀 big mwah to the ./drivers/regulator crew, this page is dated October 2026, and the whole thing lives under regulator_ir...event_simple(9) — stay slay, stay regulated 🔥💖