event_device_notify(9)

💖 event_device_notify(9) 💖

okay so welcome to the Kernel API Manual, bestie — this is the page for event_device_notify, and yes it's a kernel function so we're doing Big Girl Unix today 🎀

---

✨ NAME ✨

event_device_notify — the callback that fires when the EC generates an event over ACPI. literally its whole job 🫶

---

🌸 SYNOPSIS 🌸

void event_device_notify (acpi_handle handle , u32 value , void *data );

no cap, that's the whole signature. three args, returns nothing, moves on with its life 💅

---

🦋 ARGUMENTS 🦋

• handle — the ACPI handle of the device that the event is coming from. like, which device is being all chatty rn 👀
• value — the value passed to Notify in ACPI. that's the notification code, iykyk ✨
• data — the notify handler data. the little payload that gets handed along 🎀

---

⭐ DESCRIPTION ⭐

okay so here's the tea: this function reads the events from the device and enqueues them. that's it, that's the whole vibe — grab the events, toss 'em in the queue, done. main character energy but make it a callback 🔥

---

🌈 SEE ALSO 🌈

the squad, fr fr — all hanging out in the kernel file ./drivers/platform/chrome/wilco_ec/event.c:

• struct ec_event(9)
• struct ec_event_queue(9)
• struct event_device_data(9)
• enqueue_events(9)
• event_read(9)
• free_device_data(9)
• event_device_probe(9)

go read them, they're iconic 👑

---

and that's the page bestie 🍓 big sign-off energy: this one comes from ./drivers/platform/chrome/wilc... and it's dated October 2026, with event_device_notify(9) right there in the corner like the little legend it is. mwah 💋🧚💜