i3c_master_dma_map_single(9)

📦 version 7.3.1, in nixpkgs unstable

okay so you found the Kernel API Manual page for i3c_master_dma_map_single, and honestly? It’s giving “tiny but important DMA helper” energy 🫶💅

💖 NAME 💖

i3c_master_dma_map_single — map a buffer for a single DMA transfer. Slay.

✨ SYNOPSIS ✨

struct i3c_dma * i3c_master_dma_map_single (struct device *dev , void
       *buf , size_t len , bool force_bounce , enum dma_data_direction dir );

🎀 ARGUMENTS 🎀

  • dev — the device object of a device doing DMA. Main character device energy ✨
  • buf — the destination/source buffer for DMA. It’s literally the buffer bestie 💅
  • len — length of transfer. Gotta know how much we’re moving 🫶
  • force_bounce — true means force to use a bounce buffer; false means the function will auto check is a bounce buffer required. She’s flexible like that 💖
  • dir — DMA direction. Which way are we going? 👀

🌸 DESCRIPTION 🌸

Map buffer for a DMA transfer and allocate a bounce buffer if required. That’s the whole vibe: map it, and if a bounce buffer is required, she allocates one 🦋

💅 RETURN 💅

I3C DMA transfer descriptor or NULL in case of error. So you either get the descriptor or a lil NULL heartbreak 😭

🦋 SEE ALSO 🦋

Kernel file ./drivers/i3c/master.c is part of the friend group, along with:

okay bye bestie — this page’s source/version is ./drivers/i3c, it’s dated October 2026, and it’s the i3c_master_dma_map_single(9) page. mwah 💋✨

📦 where this page comes from