devm_spi_of...est_dma_chan(9)

💅 devm_spi_offload_tx_stream_request_dma_chan 💅

okay bestie, so this is a page straight out of the Kernel API Manual, and it's about one very specific little function: devm_spi_offload_tx_stream_request_dma_chan. say it with me. it's a mouthful. it ate though. 🫶

---

✨ NAME ✨

devm_spi_offload_tx_stream_request_dma_chan — grab the DMA channel info for the TX stream, bestie, that's the whole job 🎀

---

🌸 SYNOPSIS 🌸

struct dma_chan * devm_spi_offload_tx_stream_request_dma_chan (struct
device *dev , struct spi_offload *offload );

like, look at her. struct dma_chan *. she returns a pointer. main character behavior honestly 👑

---

🦋 ARGUMENTS 🦋

• dev — the Device, here for devm purposes. that's it, that's the vibe, it's the managed-lifetime plug 💖
• offload — the Offload instance. the little guy we're asking about.

---

💀 DESCRIPTION 💀

so here's the tea ☕: this is the DMA channel that will provide data to transfers that use the SPI_OFFLOAD_XFER_TX_STREAM offload flag. no cap, that's the entire lore. she's the data supplier for those TX stream transfers, periodt ✨

---

🔥 RETURN 🔥

Pointer to DMA channel info — or a negative error code 😭 (so like, check it, don't just yolo it into a dereference, i'm begging 🙈)

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/spi/spi-offload.c (the source of truth, go read her 💜)
• devm_spi_offload_alloc(9)
• devm_spi_offload_get(9)
• devm_spi_offload_trigger_get(9)
• spi_offload_trigger_validate(9)
• spi_offload_trigger_enable(9)
• spi_offload_trigger_disable(9)
• devm_spi_offload_rx_stream_request_dma_chan(9) (her sibling!! the RX one 🧚)
• devm_spi_offload_trigger_register(9)
• spi_offload_trigger_get_priv(9)

---

ok that's the page!! every flag, every name, every reference stayed exactly where it belongs — i just gave it a little glitter 💅

and finally, the cute little sign-off: this one lives in ./drivers/spi, it's dated October 2026, and it's part of the Kernel API Manual. slay, go read your DMA channels, mwah 🍓💖