__ssp_receive_chars(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– __ssp_receive_chars(9) πŸ’–

okay so this is a page from the Kernel API Manual bestie, and it's literally all about snatching bytes off the UART. let's get into it 🫢


✨ NAME ✨

__ssp_receive_chars β€” receive multiple bytes from the UART. yes, plural, she's not doing one-at-a-time energy πŸ’…


🌸 SYNOPSIS 🌸

void __ssp_receive_chars (struct sifive_serial_port *ssp );

that's it. that's the whole vibe. void return, one arg, no notes πŸ’œ


πŸŽ€ ARGUMENTS πŸŽ€

  • ssp β€” pointer to a struct sifive_serial_port. like, that's the whole thing. she just wants her struct, okay? πŸ¦‹

⭐ DESCRIPTION ⭐

so here's the tea fr fr: this function receives up to an RX FIFO's worth of bytes from the SiFive UART that ssp is referring to, and then passes them up to the Linux serial layer. 🧚

"up to an RX FIFO's worth" is the key phrase β€” not more, not less, just what the FIFO's giving. she's doing exactly as much work as the hardware allows and then handing it off. iconic behavior honestly πŸ‘‘


πŸ”₯ CONTEXT πŸ”₯

expects ssp->port.lock to be held by the caller. like, you hold the lock, bestie, not her. she is NOT acquiring it for you. if you forgot, that's a you problem 😭

🌈 SEE ALSO 🌈

okay this list is LONG and honestly kind of a squad πŸ’€ let's go:

like, go read those too, they're all part of the same little friend group 🀝


and that's the whole page!! this lil icon comes from ./drivers/tty/serial, dated October 2026, and the manual name is __ssp_receive_chars(9) β€” so if you ever need to remember where you read this, it's right there in the corner bestie πŸŽ€βœ¨πŸ’–

πŸ“¦ where this page comes from