cros_ec_irq_handler(9)

💅 cros_ec_irq_handler(9) — like, the Kernel API Manual page, bestie

okay so picture this: you're deep in the kernel, in the Kernel API Manual, and you've stumbled onto cros_ec_irq_handler. she's the top half part of the interrupt handler ✨ that's the whole vibe, that's the NAME section, we're done here. no but fr fr keep reading, there's a whole synopsis situation.

---

✨ SYNOPSIS ✨

irqreturn_t cros_ec_irq_handler (int irq , void *data );

like, that's it. that's her. iconic signature, no notes 💅

---

🎀 ARGUMENTS 🎀

• irq — the IRQ id. literally just the id of the IRQ, that's it, that's the whole thing 🦋
• data — the (ec_dev) device that's got events to process. so like, this is where the actual event-having device lives 👑

---

🔥 RETURN 🔥

wakeup the bottom half 😭 that's the return value's whole personality — it wakes up the bottom half. periodt.

ngl this is the "top half" of the handler, so the actual heavy lifting gets handed off — this one just does the wakeup and dips 🙈

---

🌸 SEE ALSO 🌸

kernel file ./drivers/platform/chrome/cros_ec.c — and honestly the whole cros_ec friend group is here, they all show up together iykyk:

• cros_ec_handle_event(9)
• cros_ec_irq_thread(9)
• cros_ec_register(9)
• cros_ec_unregister(9)
• cros_ec_suspend_prepare(9)
• cros_ec_suspend_late(9)
• cros_ec_suspend(9)
• cros_ec_resume_complete(9)
• cros_ec_resume_early(9)
• cros_ec_resume(9)

---

and that's the page, bestie 🫶 she lives in ./drivers/platform/chrome, she's dated October 2026, and this whole little kernel-API-manual moment was brought to you from right there in that directory. go drink some water and go read cros_ec.c 💖