STRUCT STM32_I2C_DMA(9)

💖 NAME 💖

struct stm32_i2c_dma — the DMA-specific data, bestie. Like, this is the little struct that holds all the direct-memory-access deets for the STM32 I2C driver. No cap.

Ok so real talk, this page lives in the Kernel API Manual, section 9 — very demure, very kernel-space. 🧚

✨ SYNOPSIS ✨

Here's the whole vibe, verbatim, don't touch a character:

struct stm32_i2c_dma {
    struct dma_chan *chan_tx;
    struct dma_chan *chan_rx;
    struct dma_chan *chan_using;
    dma_addr_t dma_buf;
    unsigned int dma_len;
    enum dma_transfer_direction dma_transfer_dir;
    enum dma_data_direction dma_data_dir;
    struct completion dma_complete;
 };

Look at her. Eight members. Absolutely iconic. 👑

🎀 MEMBERS 🎀

Ok let's meet the cast, one by one, main-character energy only:

• chan_tx — the dma channel for TX transfer 💅 like, the dedicated send-it channel
• chan_rx — the dma channel for RX transfer 🫶 the dedicated receive-it channel
• chan_using — the dma channel that's actually being used for the current transfer (so that's either TX or RX, depending on the moment) ⭐
• dma_buf — the dma buffer 🌸 that's where the bytes live
• dma_len — the dma buffer len 📏 literally the length, that's it, that's the whole job
• dma_transfer_dir — the dma transfer direction indicator 🧭 (an enum dma_transfer_direction, fyi)
• dma_data_dir — the dma transfer mode indicator 🌈 (an enum dma_data_direction, if we're being precise)
• dma_complete — the dma transfer completion ✅ this one's a struct completion, i.e. how you know the transfer is done-done

Ngl bestie, nothing here is dangerous — it's just a data struct. The only danger is forgetting to wait on dma_complete and then wondering why your buffer is sus. 😭

🦋 SEE ALSO 🦋

• Kernel file ./drivers/i2c/busses/i2c-stm32.h — go read the header, iykyk 🔥

Ok that's the whole page, mwah 💋 — this masterpiece came from ./drivers/i2c/busses, dated October 2026, and it's your girl struct stm32_i2c_dma(9) signing off. Periodt. 🎀✨