ir_rc5_encode(9)

💅 ir_rc5_encode(9)

okay so bestie, welcome to the Kernel API Manual — yes that's the whole manual name, we're fancy now 🎀 — and today's main character is ir_rc5_encode, a function that takes a scancode and turns it into a whole lil stream of raw events. it's giving translator energy, fr fr.

✨ NAME ✨

ir_rc5_encode — encode a scancode as a stream of raw events 🦋

✨ SYNOPSIS ✨

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

that's it, that's the whole vibe check. one int coming back at you, four args going in 💅

✨ ARGUMENTS ✨

• protocol — the protocol variant you wanna encode with. like, which flavour we're doing here 🌸
• scancode — the actual scancode to encode. the thing we're translating, periodt.
• events — an array of raw ir events to write into. this is where the output goes, no cap.
• max — the maximum size of events. basically how much room you've got to work with 🙈

✨ RETURN ✨

so what comes back?

• the number of events written 💖 that's the happy path, slay.
• -ENOBUFS — if there isn't enough space in the array to fit the encoding 😭 and listen, in this case all max events will have been written. so yeah, you filled it up completely, wig.
• -EINVAL — if the scancode is ambiguous or invalid 💀 no guesses, no vibes, just an error.

ngl bestie, keep an eye on that -ENOBUFS situation — it's not "nothing happened", it's "the whole array got used and then it complained" 👑

🌈 SEE ALSO 🌈

• Kernel file ./drivers/media/rc/ir-rc5-decoder.c
• ir_rc5_decode(9) — the reverse vibe, iykyk

and that's the page, bestie 🫶 brought to you by ./drivers/media/rc, October 2026 edition ⭐ go forth and encode responsibly, mwah 💜