lirc_scancode_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« lirc_scancode_event(9) πŸ’«

okay so bestie, welcome to the Kernel API Manual β€” this is the page for lirc_scancode_event, and it's honestly such a little icon. short page, big main character energy. let's get into it πŸŽ€


✨ NAME ✨

lirc_scancode_event β€” send scancode data to lirc so it can be relayed to userspace πŸ’Œ and yes, the best part: this can be called in atomic context. no cap, that's the whole point of it, she's built different.


🌸 SYNOPSIS 🌸

void lirc_scancode_event (struct rc_dev *dev , struct lirc_scancode *lsc
);

like, look at her. void return, two pointers, zero drama. periodt πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the struct rc_dev descriptor of the device 🫢 you know, the remote-control device thingy. this is who's sending the vibes.
  • lsc β€” the struct lirc_scancode describing the decoded scancode ✨ this is the actual scancode info getting passed along, all decoded and ready to slay.

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./drivers/media/rc/lirc_dev.c β€” the source file, go read her, she's iconic πŸ”₯
  • lirc_raw_event(9) β€” the raw counterpart, lowkey her sibling. iykyk πŸ’œ

🫢 friendly reminder bestie: lirc_scancode_event is the decoded scancode one, and the whole selling point is that you can call it in atomic context. don't forget that part, it's giving important πŸ’€

and that's the page!! mwah πŸ’– this lil beauty lives in ./drivers/media/rc, dated October 2026, and she's filed under lirc_scancode_event(9) if you ever need to find her again. go be great, bestie ⭐🧚🌸

πŸ“¦ where this page comes from