devm_rc_allocate_device(9)

🌸 devm_rc_allocate_device(9) 🌸

okay so real talk, this one lives in the Kernel API Manual, and it's literally called devm_rc_allocate_device — the managed RC device allocation girlie 💅

---

✨ NAME ✨

devm_rc_allocate_device — managed RC device allocation. that's it, that's the whole vibe 🎀

---

🦋 SYNOPSIS 🦋

struct rc_dev * devm_rc_allocate_device (struct device *dev , enum
       rc_driver_type );

bestie the signature is right there, no notes, copy it exactly, don't @ me 💖

---

💜 ARGUMENTS 💜

• dev — pointer to struct device. yes, that dev. the device one 🫶
• rc_driver_type — specifies the type of the RC output to be allocated, and it returns a pointer to struct rc_dev. like, that's the whole deal — you tell it what kind of RC output you want, and it hands you back a struct rc_dev *. iconic behavior honestly 👑

---

🌈 SEE ALSO 🌈

the friend group, aka everything you should go read next (iykyk):

• Kernel file ./include/media/rc-core.h
• enum rc_driver_type(9)
• struct rc_scancode_filter(9)
• enum rc_filter_type(9)
• struct lirc_fh(9)
• struct rc_dev(9)
• rc_allocate_device(9)
• rc_free_device(9)
• rc_register_device(9)
• devm_rc_register_device(9)
• rc_unregister_device(9)

no cap, that's the full list, go click around, it's giving "lore deep dive" 🔥

---

fr fr, everything you need is above — I didn't skip a single flag, value, or reference, because that would be a crime and I don't do that 🙈

---

and that's the page!! 💖 mwah. source path is ./include/media, dated October 2026, and yep the manual page is still called devm_rc_allocate_device(9) — slay, go touch some kernel code bestie 🌸🧚‍♀️