stm32_spi_transfer_one_dma(9)

📦 version 7.3.1, in nixpkgs unstable

💅 stm32_spi_transfer_one_dma — from the Kernel API Manual, bestie ✨

Okay so picture this: we're deep in the kernel, in the manual page for stm32_spi_transfer_one_dma(9), and honestly? It's giving "one job, done with DMA." Let me walk you through it 🫶

✨ NAME ✨

stm32_spi_transfer_one_dma — transfer a single spi_transfer using DMA

Like, one transfer. Singular. But it's doing it with DMA, so it's lowkey the cool one 🎀

🌸 SYNOPSIS 🌸

int stm32_spi_transfer_one_dma (struct stm32_spi *spi , struct
spi_transfer *xfer );

Look at that signature. Two pointers, one int coming back at you. Slay 💅

🦋 ARGUMENTS 🦋

  • spi — pointer to the spi controller data structure. This is the main character, the controller itself, everything you need to know about the SPI hardware lives in here 👑
  • xfer — pointer to the spi_transfer structure. The actual transfer you're pushing through. This is what we're moving ✨

💖 DESCRIPTION 💖

Here's the whole vibe check: it must return 0 if the transfer is finished, or 1 if the transfer is still in progress.

That's it. That's the rule. Not me making up a third option — it's 0 or 1, periodt. So when you call this you know where you stand: done, or still cooking 🔥

No cap, that "must" is doing a lot of work in that sentence. Respect it.

🌈 SEE ALSO 🌈

Buckle up bestie, this is the friend group and it's huge 💀 All from the kernel file ./drivers/spi/spi-stm32.c:

Like I said. Enormous. But every single one of them is invited to the party 🧚💜

And that's the page, bestie ✨ This little gem lives in ./drivers/spi, and it's dated October 2026 — so like, future iconic. Go forth and transfer one SPI thing with DMA, you absolute legend 💅💖🎀

📦 where this page comes from