rmi_unregis...sport_device(9)

💅 rmi_unregister_transport_device — Kernel API Manual edition 🎀

okay so bestie, welcome to the rmi_unregis...sport_device(9) page — yes that's the truncated little header name, she's shy but she's iconic. This is the Kernel API Manual and honestly it's a short one, so grab your strawberry drink 🍓 and let's go.

---

✨ NAME ✨

rmi_unregister_transport_device — unregister a transport device connection 💫

like, she un-registers. the opposite of registering. the breakup arc. no cap.

---

✨ SYNOPSIS ✨

void rmi_unregister_transport_device (struct rmi_transport_dev *xport );

that's it. that's the whole vibe check. one function, void, no return value, she does her thing and dips 🫶

---

✨ ARGUMENTS ✨

• xport — the transport driver to unregister 👑 this is the struct rmi_transport_dev * you're handing over, and she is literally the main character of this call.

---

✨ SEE ALSO ✨

• Kernel file ./drivers/input/rmi4/rmi_bus.c 📁 (go read the source, iykyk)
• rmi_register_transport_device(9) — the reverse operation, the "we're so back" to this one's "it's over" 😭
• __rmi_register_function_handler(9)
• rmi_unregister_function_handler(9)

---

okay that's the whole page, short and sweet, she ate and left no crumbs 🌸 ngl this one was a quick read. mwah 💋

sign-off time bestie: this lil beauty lives in ./drivers/input/rmi4 and she's dated October 2026 ⭐ don't forget her 🎀💜