__ssp_transmit_char(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __ssp_transmit_char β€” a kernel API manual moment

okay so bestie, we're in the kernel API manual, specifically section 9, and today's main character is __ssp_transmit_char ✨ it's a tiny little function that just... puts a byte in a FIFO. and honestly? iconic behaviour. no cap.


🌸 NAME 🌸

__ssp_transmit_char β€” enqueue a byte to transmit onto the TX FIFO πŸŽ€


✨ SYNOPSIS ✨

void __ssp_transmit_char (struct sifive_serial_port *ssp , int ch );

like, that's the whole signature. void return, so it gives you nothing back β€” it's giving "I did the thing, don't ask questions" energy πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ssp β€” pointer to a struct sifive_serial_port. this is your lil serial port buddy that you're transmitting on 🫢
  • ch β€” the character to transmit. one (1) single character. that's it. that's the byte πŸ’–

πŸ‘‘ DESCRIPTION πŸ‘‘

So what it actually does: it enqueues a byte ch onto the transmit FIFO, given a pointer ssp to the struct sifive_serial_port * you wanna transmit on. simple. slay. one byte, one FIFO, done ✨

⚠️ but bestie listen β€” the caller should first check to make sure the TXFIFO actually has space before calling this. the manual literally points you at sifive_serial_is_txfifo_full for that check. check first, transmit second, that's the rule πŸ™ˆ

🌈 CONTEXT 🌈

Any context. fr fr, that's it β€” any context at all. no restrictions, no "only from interrupt context" drama, nothing. go off πŸ’€


πŸŽ€ SEE ALSO πŸŽ€

the full squad, no gatekeeping:

like a whole friend group of ssp functions, and you should lowkey go read them all 🧚


and that's the page!! πŸ’œ it lives over in ./drivers/tty/serial, dated October 2026, and it's titled __ssp_transmit_char(9) β€” mwah, that's a wrap, periodt πŸ“βœ¨

πŸ“¦ where this page comes from