stm32h7_spi_read_rxfifo(9)

📦 version 7.3.1, in nixpkgs unstable

💅 stm32h7_spi_read_rxfifo — a Kernel API Manual moment

okay bestie, welcome to the Kernel API Manual, where we read manpages for breakfast and slay 🎀. This one is short and sweet and honestly kind of iconic.

✨ NAME ✨

stm32h7_spi_read_rxfifo — literally just: read bytes in the Receive Data Register 🦋

✨ SYNOPSIS ✨

void stm32h7_spi_read_rxfifo (struct stm32_spi *spi );

that's it. that's the whole function signature. no return value, she returns void, she's mysterious, she's lowkey about it 💅

✨ ARGUMENTS ✨

  • spi — pointer to the spi controller data structure. that's the whole thing, bestie — you hand her the controller struct and she goes to work 🫶

✨ DESCRIPTION ✨

So what does she actually do? She writes into rx_buf, and the amount she writes depends on how many bytes are still remaining (ngl, this is the important safety bit) — and the reason is so she doesn't write beyond the end of rx_buf 😭🙈. Like, no buffer overrun today, we're being responsible in this group chat.

fr fr, that "remaining bytes" check is the whole personality of this function — it's the guardrail, not a detail. do not skip it, do not "clean it up", do not pass go 💀

✨ SEE ALSO ✨

okay this is the part where the manpage dumps her entire friend group on us, and we're gonna list every single one because nobody gets left behind 👑🌈

like, that's a lot of siblings but every one of them is valid and we respect them all 🧚💜

and that's the whole page, babes — sourced straight from ./drivers/spi, dated October 2026, in the Kernel API Manual. periodt. go read some registers, you've got this 🌸💖

📦 where this page comes from