__ssp_transmit_chars(9)

🎀 __ssp_transmit_chars(9) 🎀

okay so bestie, welcome to the Kernel API Manual — this page is literally about __ssp_transmit_chars, and it is giving “make room, bytes are coming” energy. 💅✨

💖 NAME 💖

__ssp_transmit_chars — enqueue multiple bytes onto the TX FIFO 🫶

🌈 SYNOPSIS 🌈

void __ssp_transmit_chars (struct sifive_serial_port *ssp );

🦋 ARGUMENTS 🦋

• ssp — pointer to a struct sifive_serial_port ✨

🔥 DESCRIPTION 🔥

So what’s the vibe? It transfers up to a TX FIFO size’s worth of characters from the Linux serial transmit buffer to the SiFive UART TX FIFO. That’s the whole move: multiple bytes, enqueued, iconic. 👑

No cap, the “up to a TX FIFO size’s worth” part is important — that’s literally what the page says, and I’m not adding extra lore. 💀

🧚 CONTEXT 🧚

Any context. Expects ssp->port.lock to be held by caller. 🔒

Like, any context, but bestie — the caller has to be holding that lock. Do not forget the lock. 🫶

👑 SEE ALSO 👑

Kernel file ./drivers/tty/serial/sifive.c, plus these related icons:

• struct sifive_serial_port(9)
• __ssp_early_writel(9)
• __ssp_early_readl(9)
• __ssp_writel(9)
• __ssp_readl(9)
• sifive_serial_is_txfifo_full(9)
• __ssp_transmit_char(9)
• __ssp_enable_txwm(9)
• __ssp_enable_rxwm(9)
• __ssp_disable_txwm(9)
• __ssp_disable_rxwm(9)
• __ssp_receive_char(9)
• __ssp_receive_chars(9)
• __ssp_update_div(9)
• __ssp_update_baud_rate(9)
• __ssp_set_stop_bits(9)
• __ssp_wait_for_xmitr(9)
• sifive_serial_clk_notifier(9)

---

xoxo bestie 💖 — source/version: ./drivers/tty/serial; date: October 2026; page: __ssp_transmit_chars(9). periodt 🎀