enqueue_events(9)

💅 enqueue_events(9) — the kernel API manual, bestie edition

Okay so real talk: this is enqueue_events from the Kernel API Manual, section 9, and it's the lil function that takes EC events and drops them in the queue so userspace can finally read them. She's a middle man. She's a vibe courier. Let's get into it. 🎀

---

✨ NAME ✨

enqueue_events — place EC events in queue to be read by userspace.

Yep, that's the whole job. She puts the events in the queue. Userspace reads them later. Slay, honestly. 💅

---

🦋 SYNOPSIS 🦋

int enqueue_events (struct device *dev , const u8 *buf , u32 length );

Three args, one int coming back at you. That's the whole signature, no notes. ✨

---

🌸 ARGUMENTS 🌸

• dev — the device the events came from. Gotta know who's calling, right? 🫶
• buf — the buffer of event data. This is where the actual events are chilling.
• length — the length of the event data buffer. She needs to know how much buf there is, that's just math bestie.

---

🧚 DESCRIPTION 🧚

Okay so here's the tea. ☕

buf contains a number of ec_event's, packed one after the other. Like sardines. Like besties in a photobooth. 🎀

Each ec_event is of variable length — so no, you can't just assume they're all the same size and vibe-check your way through, that's not how this works.

The algorithm, in order,因为她's thorough:

1. Start with the first event.
2. Copy it into a persistent ec_event.
3. Store that entry in the queue.
4. Move on to the next ec_event in buf.
5. Repeat.

Copy, store, next, repeat. Copy, store, next, repeat. It's giving "loop with main character energy." 🔥

The "persistent" part is doing a LOT of work there ngl — the event gets copied out so it survives, because buf is not gonna be around forever. 🙈

---

🌈 RETURN 🌈

• 0 — on success 🎉
• negative error code — on failure 😭 (yeah she can fail, and when she does she reports back with a negative number, periodt)

---

👑 SEE ALSO 👑

The kernel file ./drivers/platform/chrome/wilco_ec/event.c — that's the neighborhood this whole thing lives in, go say hi. 🏡

And the rest of the squad:

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

iykyk 💜

---

And that's the page, bestie! 🫶 Cute lil sign-off time: this one comes to you from ./drivers/platform/chrome/wilc... (yes it got cut off in the original, tragic, RIP) and it's dated October 2026. Live laugh love, and may your ec_events always be correctly parcelled out. 🎀✨💖