ir_sanyo_decode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ir_sanyo_decode(9) β€” Kernel API Manual

okay so bestie, welcome to ir_sanyo_decode, straight out of the Kernel API Manual ✨ β€” this is the SANYO decoder page and it's short but she serves.


🌸 NAME 🌸

ir_sanyo_decode β€” decode one SANYO pulse or space πŸŽ€

Like, literally one. One single pulse. Or one single space. That's her whole job and she does it flawlessly πŸ’…


✨ SYNOPSIS ✨

int ir_sanyo_decode (struct rc_dev *dev , struct ir_raw_event ev );

that's it. that's the whole signature. she takes two things and returns an int, periodt 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the struct rc_dev descriptor of the device πŸŽ€ this is the main character β€” the remote-control device struct she's decoding for, iykyk.
  • ev β€” the struct ir_raw_event descriptor of the pulse/space ⭐ this is the actual pulse or space being handed over, one at a time, no cap.

πŸ’– DESCRIPTION πŸ’–

So the way that this works is: she takes one SANYO pulse or space, feeds it through, and if the pulse violates the state machine she returns -EINVAL πŸ’€

That's the whole vibe check β€” the state machine is the queen and if you break her rules you get -EINVAL, end of story πŸ™ˆ

no cap, that's literally the only documented return behaviour here: -EINVAL on a state machine violation. don't come for her, she's doing her best πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./drivers/media/rc/ir-sanyo-decoder.c πŸ¦‹ β€” go read her source, she's iconic
  • ir_sanyo_encode(9) πŸ”₯ β€” the other half of the duo, the encoder bestie

and that's the page!! 🌈 brought to you by ./drivers/media/rc, dated October 2026, titled ir_sanyo_decode(9) β€” mwah, sending you a forehead kiss, go decode some pulses πŸ“πŸ’œπŸ§š

πŸ“¦ where this page comes from