devm_spi_offload_get(9)

💅 devm_spi_offload_get 💅

okay so bestie, this is the Kernel API Manual entry for devm_spi_offload_get(9), and it's giving “small function, very important energy” ✨

🌸 NAME 🌸

devm_spi_offload_get — get an offload instance, periodt 💖

✨ SYNOPSIS ✨

struct spi_offload * devm_spi_offload_get (struct device *dev , struct
spi_device *spi , const struct spi_offload_config *config );

🎀 ARGUMENTS 🎀

• dev — the device, here for devm purposes 🫶
• spi — the SPI device you're using for the transfers 🌈
• config — the offload configuration, no cap 💅

🦋 DESCRIPTION 🦋

Peripheral drivers call this function to get an offload instance that meets the requirements specified in config. Literally that's the whole vibe 😌

If no suitable offload instance is available, -ENODEV is returned. Not dramatic, just facts 💀

👑 RETURN 👑

An offload instance when it slays, or an error on failure 😭

🔥 SEE ALSO 🔥

• Kernel file ./drivers/spi/spi-offload.c
• devm_spi_offload_alloc(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_tx_stream_request_dma_chan(9)
• devm_spi_offload_rx_stream_request_dma_chan(9)
• devm_spi_offload_trigger_register(9)
• spi_offload_trigger_get_priv(9)

mwah 💋 that's the whole page, sourced from ./drivers/spi, dated October 2026, and yeah — devm_spi_offload_get(9) ate and left no crumbs 🍓🧚💜