serdev_controller_remove(9)

💅 serdev_controller_remove(9)

okay bestie, so this page lives in the Kernel API Manual — it's the serdev_controller_remove page, and yes it's a whole vibe 💖

---

✨ NAME ✨

serdev_controller_remove — remove an serdev controller 🎀

(not me copying the grammar exactly, the original says "an serdev controller" and I'm not about to gaslight you into thinking it says "a" — we keep it fr fr)

---

🌸 SYNOPSIS 🌸

void serdev_controller_remove (struct serdev_controller *ctrl );

bestie it literally returns nothing (void), it just goes in and does the thing ✨

---

🦋 ARGUMENTS 🦋

• ctrl — the controller to remove 👑 this is the main character of the whole operation

---

💜 DESCRIPTION 💜

So the way that this works: you call this to remove an serdev controller. That's it, that's the job 🌈

⚠️ but listen, this part is important and I'm not gonna let you skip it: the caller is responsible for calling serdev_controller_put to discard the allocated controller. Like, you gotta clean up after yourself, no cap. This function is not gonna do it for you 🫶

---

🍓 SEE ALSO 🍓

Kernel file ./drivers/tty/serdev/core.c — and here's the whole friend group, go say hi 💅

• serdev_device_add(9)
• serdev_device_remove(9)
• serdev_device_write_buf(9)
• serdev_device_write(9)
• serdev_device_alloc(9)
• serdev_controller_alloc(9)
• of_find_serdev_controller_by_node(9)
• serdev_acpi_get_uart_resource(9)
• serdev_controller_add(9)
• __serdev_device_driver_register(9)

---

and that's the whole page babe, you ate that 🧚✨ sign-off time: this one hangs out in ./drivers/tty/serdev, dated October 2026, and it's all about serdev_controller_remove(9) 💖🌷⭐