serdev_device_write_buf(9)

📦 version 7.3.1, in nixpkgs unstable

💖 serdev_device_write_buf 💖

okay so bestie, welcome to the Kernel API Manual — yes you're literally reading kernel docs rn and I'm so proud of you 🫶 this one's about serdev_device_write_buf, no cap.

✨ NAME ✨

serdev_device_write_buf — write data asynchronously, i.e. you hand off your bytes and do not sit around waiting for them, because you have main character energy and other things to do 💅

🦋 SYNOPSIS 🦋

int serdev_device_write_buf (struct serdev_device *serdev , const u8
*buf , size_t count );

🎀 ARGUMENTS 🎀

  • serdev — the serdev device, your little guy, the one you're writing to 💖
  • buf — the data to be written, aka your bytes, your content, your moment
  • count — number of bytes to write. how many. the quantity. be honest about it

🌸 DESCRIPTION 🌸

Write data to the device asynchronously. You drop the bytes off and you leave. Iconic behaviour, honestly.

⚠️ lowkey important, bestie: any accepted data has only been buffered by the controller — like, it's in the building, but it is NOT out the door yet. So if you actually need to know the controller write buffer has been emptied for real, use serdev_device_wait_until_sent. Do not skip this step. This is the vibe check your data needs 😭

⭐ RETURN ⭐

The number of bytes written — which is less than count if there wasn't enough room in the write buffer (not a glow-up moment, but it happens) — or a negative errno on errors 💀

🔥 SEE ALSO 🔥

Kernel file ./drivers/tty/serdev/core.c — go read it, iykyk 📖

that's the whole page, bestie — go buffer some bytes responsibly 🧚

mwah 💋 this has been the serdev_device_write_buf(9) page, living in ./drivers/tty/serdev, dated October 2026, brought to you by the Kernel API Manual. slay, bye 👑

📦 where this page comes from