img_ir_decoder_compatible(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… img_ir_decoder_compatible(9) ✨

okay so bestie, welcome to the Kernel API Manual β€” this one's a little function with one (1) job and it does it slayfully. It's called img_ir_decoder_compatible, and yes, that name is a mouthful, but it's literally just asking: "hey, will this decoder actually work with this device?" vibe check energy fr fr πŸŽ€


🌸 NAME 🌸

img_ir_decoder_compatible β€” Find whether a decoder will work with a device. That's it, that's the whole mission, and honestly? Iconic. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

bool img_ir_decoder_compatible (struct img_ir_priv *priv , const struct img_ir_decoder *dec );

Look at her. Returns a bool, takes two pointers, no drama, no cap. πŸ’–


✨ ARGUMENTS ✨

  • priv β€” the IR private data. Like, the device's whole personal little world of IR info. 🫢
  • dec β€” the decoder you're checking. The one you're side-eyeing and going "hmm, are you compatible or not?" πŸ™ˆ

πŸ’œ RETURN πŸ’œ

Returns true if dec is compatible with the device that priv refers to. That's the whole answer bestie β€” true means yes, they're a match, main character couple energy. 🌈

lowkey important: it's a bool, so don't go expecting anything fancier than a true/false situation. Keep it simple, periodt. πŸ’…

πŸ”₯ SEE ALSO πŸ”₯

The kernel file lives at ./drivers/media/rc/img-ir/img-ir-hw.c β€” go say hi to her sometime. And here's the whole friend group, all 14 of them, not one skipped because we don't do that here:


okay that's the whole page, you ate that bestie πŸ“ this little function comes to you straight from ./drivers/media/rc/img-ir, dated October 2026 β€” mwah, go forth and check your decoders πŸ’–πŸ§šβ€β™€οΈβœ¨

πŸ“¦ where this page comes from