stm32_spi_can_dma(9)

📦 version 7.3.1, in nixpkgs unstable

💅 stm32_spi_can_dma(9) 💅

Okay bestie, welcome to the Kernel API Manual — this one's a little kernel function called stm32_spi_can_dma, and honestly? It's giving "tiny gatekeeper with one job." Let's get into it 🎀

✨ NAME ✨

stm32_spi_can_dma — literally just: determine if the transfer is eligible for DMA use 💫

🌸 SYNOPSIS 🌸

bool stm32_spi_can_dma (struct spi_controller *ctrl , struct spi_device
*spi_dev , struct spi_transfer *transfer );

It returns a bool, bestie — so it's a yes-or-no girlie, no in-between 💅

🦋 ARGUMENTS 🦋

  • ctrl — the controller interface 👑 (the big boss of the SPI situation)
  • spi_dev — pointer to the spi device 🎀 (your actual lil device)
  • transfer — pointer to spi transfer 🧚 (the thing being moved, obviously)

💖 DESCRIPTION 💖

So here's the tea, fr fr:

If the driver has a fifo and the current transfer size is greater than the fifo size, use DMA. Otherwise, use DMA for a transfer longer than the defined DMA min bytes. No cap, that's the whole vibe check 🔥

Lowkey a two-branch decision and it ate. Periodt. ⭐

🌈 SEE ALSO 🌈

Kernel file ./drivers/spi/spi-stm32.c — and bestie, the friend group is huge, we're listing every single one 🫶:

Like I said. Enormous friend group. iykyk 💀✨

That's the whole page, bestie — she's short, she's sweet, and she knows exactly what she's about 💜

Sign-off time 🎀: this lil beauty lives in ./drivers/spi, dated October 2026, and the whole thing is the stm32_spi_can_dma(9) page, manual and all. Slay 🦋👑

📦 where this page comes from