serdev_device_alloc(9)

💖 serdev_device_alloc(9) 💖

Hey bestie, welcome to the Kernel API Manual ✨ — this is the one about serdev_device_alloc, and ngl it's a short one but it's lowkey important, so let's get into it 🫶

---

🌸 NAME 🌸

serdev_device_alloc — allocate a new serdev device 🎀

---

✨ SYNOPSIS ✨

struct serdev_device * serdev_device_alloc (struct serdev_controller
*ctrl );

---

🦋 ARGUMENTS 🦋

• ctrl — the associated controller 💫 (like, the controller this new device is being tied to, iykyk)

---

💅 DESCRIPTION 💅

So here's the vibe check: this function allocates you a brand-new serdev device ✨. But bestie, listen — the caller is responsible for what happens next 🙈. You've got exactly two moves, and you gotta pick one, no cap:

• call serdev_device_add to add the newly allocated controller 👑, or
• call serdev_device_put to discard it 💀

That's it. That's the whole responsibility. Don't just leave it floating there, okay? 😭

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/tty/serdev/core.c plus all these iconic little friends:

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

---

Okay that's the whole page, you ate that 💖 This little gem lives over in ./drivers/tty/serdev, and the version we're serving you is from October 2026 — stay slay, stay allocated, and remember to free your stuff, bestie 🌈💜