ir_mce_kbd_encode(9)

💅 ir_mce_kbd_encode(9)

okay so bestie, welcome to the Kernel API Manual — yes, the actual kernel, and yes, this is the page that teaches you how to encode a scancode into a stream of raw IR events. it's giving "i speak fluent infrared" energy and honestly? iconic. 🦋

---

✨ NAME ✨

ir_mce_kbd_encode — Encode a scancode as a stream of raw events 📡

like, you hand it a scancode, and it hands you back a whole lil stream of raw events. match made in heaven, fr fr.

---

🌸 SYNOPSIS 🌸

int ir_mce_kbd_encode (enum rc_proto protocol , u32 scancode , struct
      ir_raw_event *events , unsigned int max );

read it like a recipe, babes — four ingredients, one int coming back out the other side. 🎀

---

🎀 ARGUMENTS 🎀

• protocol — the protocol to encode. this is the one telling us which flavour of IR we're cooking with 💅
• scancode — the scancode to encode. the star of the show, the main character, the whole point 👑
• events — array of raw ir events to write into. this is the lil canvas you're painting on 🎨
• max — maximum size of events. the vibe check on how much room you actually have 🫶

---

💀 RETURN 💀

the number of events written. that's it, that's the win. ✨

but if there isn't enough space in the array to fit the encoding, you get -ENOBUFS 😭 — and ngl, in that case all max events will have been written, so like… it tried its best, it really did. 🙈

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/media/rc/ir-mce_kbd-decoder.c
• ir_mce_kbd_decode(9) — the decoding counterpart, the other half of the duo, the enemies-to-lovers of kernel IR code 💜

---

lowkey a reminder that -ENOBUFS still writes everything up to max — so check that return value, bestie, don't just vibe past it 💀

---

that's the whole page, periodt. 🌈 source vibes come from ./drivers/media/rc, dated October 2026, and the page itself is ir_mce_kbd_encode(9) — slay, go forth and encode responsibly 🔥👑