rio_device_remove(9)

💅 rio_device_remove(9) — the Kernel API Manual, bestie edition 🎀

okay so picture this: it's a 9 page from the Kernel API Manual, the star of the show is rio_device_remove, and she's here to tell you how a RIO device gets yeeted out of the system. no cap, that's the whole vibe. 🦋

---

✨ NAME ✨

rio_device_remove — the girl whose whole job is removing a RIO device from the system. that's it, that's the function. 🫶

---

🌸 SYNOPSIS 🌸

void rio_device_remove (struct device *dev );

literally just the one line, she's lowkey minimalist like that. ⭐

---

🎀 ARGUMENTS 🎀

• dev — the RIO device structure to match against. yes bestie, match against, that's the wording, i don't make the rules 💅

---

🔥 DESCRIPTION 🔥

so here's the tea ☕ — rio_device_remove removes a RIO device from the system. iconic behavior, no notes.

and if that device has an associated driver? 👀 then she runs the driver remove method for it. like, she's not gonna leave the driver hanging, that would be so rude.

then — and this is the part where you go "oh periodt" — she updates the reference count. that's the flow, in order, and she ate:

1. remove the RIO device from the system
2. if it has an associated driver, run the driver remove method
3. update the reference count

that's the whole function. short, sweet, main character energy. 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/rapidio/rio-driver.c
• rio_match_device(9)
• rio_dev_get(9)
• rio_dev_put(9)
• rio_device_probe(9)
• rio_register_driver(9)
• rio_unregister_driver(9)
• rio_match_bus(9)
• rio_bus_init(9)

go read those too, iykyk 🧚💜

---

and that's a wrap, bestie 🍓 this page lives over in ./drivers/rapidio, dated October 2026, and she slayed every single line of it. mwah 💋✨