i2c_put_dma_safe_msg_buf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… i2c_put_dma_safe_msg_buf(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this one's about i2c_put_dma_safe_msg_buf, and it's literally the cleanup arc of the DMA safe message buffer saga πŸŽ€


✨ NAME ✨

i2c_put_dma_safe_msg_buf β€” release the DMA safe buffer and sync it back up with the i2c_msg 🫢


🌸 SYNOPSIS 🌸

void i2c_put_dma_safe_msg_buf (u8 *buf , struct i2c_msg *msg , bool xferred );

no cap, that's the whole signature. returns void because it's a release function, she doesn't owe you a status code πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • buf β€” the buffer you got from i2c_get_dma_safe_msg_buf. and yes, it may be NULL β€” that's allowed, she's flexible like that πŸ™ˆ
  • msg β€” the message that this buffer corresponds to. they're a matched set, iykyk πŸ‘‘
  • xferred β€” a bool telling you if the message was actually transferred. true = it went through, false = it did not. simple as that fr fr ⭐

πŸ’€ SEE ALSO πŸ’€

this is the part where the friend group shows up. the whole squad, in the kernel file ./drivers/i2c/i2c-core-base.c:

like, every single one. no skipping, we don't do that here πŸ’– and obviously i2c_get_dma_safe_msg_buf(9) is the one that gave you the buffer in the first place β€” this is her put-it-back counterpart, the duo of all time 🧚


and that's the whole page, bestie!! go forth and release those buffers responsibly 🌈

source: ./drivers/i2c Β· date: October 2026 Β· this was the i2c_put_dma_safe_msg_buf(9) page from the Kernel API Manual β€” mwah, catch you on the next manpage πŸ˜­πŸ’œ

πŸ“¦ where this page comes from