STRUCT CROS_EC_UART(9)

💅 struct cros_ec_uart(9) — like, the whole vibe ✨

okay so real talk, this is a page straight out of the Kernel API Manual, and it's all about struct cros_ec_uart — the little info bundle that tells you everything about a UART-connected EC. bestie, it's giving "I know what's plugged into me and I'm not afraid to say it" 🎀

---

🌸 NAME 🌸

struct cros_ec_uart — literally just info about a uart-connected EC, that's the whole thing, no cap 💖

---

✨ SYNOPSIS ✨

here's the shape of it, copy it exactly or don't @ me:

struct cros_ec_uart {
    struct serdev_device *serdev;
    u32 baudrate;
    u8 flowcontrol;
    u32 irq;
    struct response_info response;
};

---

🦋 Members 🦋

every single field, bestie, let's go through them one by one like we're doing a vibe check 👑

• serdev — the serdev uart device we are connected to. that's our link-up, our main character connection fr 🫶
• baudrate — UART baudrate of attached EC device. u32, and yes she's important.
• flowcontrol — UART flowcontrol of attached device. tiny u8, big responsibilities 🎀
• irq — Linux IRQ number of associated serial device. that's the interrupt energy, lowkey iconic.
• response — response info passing between cros_ec_uart_pkt_xfer and cros_ec_uart_rx_bytes. she's the messenger between those two functions, periodt 💅

---

🌈 SEE ALSO 🌈

go look at these if you wanna keep reading, iykyk:

• Kernel file ./drivers/platform/chrome/cros_ec_uart.c
• struct response_info(9)

ngl, the struct over in cros_ec_uart.c is where all the actual ✨lore✨ lives — this page is just the cheat sheet 💜

---

okay that's the whole page, mwah 😘 and before you go — the source lives at ./drivers/platform/chrome and this was dated October 2026, so when you cite it in your essay make sure you get the vibes right. bye bestie, go read some kernel code 💖🦋✨