i2c_master_recv_dmasafe(9)

💖 i2c_master_recv_dmasafe 💖

okay so this is a page from the Kernel API Manual, and the star of the show is i2c_master_recv_dmasafe — one function, one job, very main character.

---

✨ NAME ✨

i2c_master_recv_dmasafe — issue a single I2C message in master receive mode using a DMA safe buffer 🦋

---

✨ SYNOPSIS ✨

int i2c_master_recv_dmasafe (const struct i2c_client *client , char *buf
, int count );

---

✨ ARGUMENTS ✨

• client — handle to the slave device 💅 like, your way in
• buf — where to store data read from the slave. it must be safe to use with DMA, no exceptions bestie 🫶
• count — how many bytes to read. has to be less than 64k since msg.len is u16 😭 that's the ceiling, respect it

---

✨ DESCRIPTION ✨

Returns a negative errno, or else the number of bytes read. that's it, that's the whole vibe ✨

---

✨ SEE ALSO ✨

Kernel file ./include/linux/i2c.h and the whole squad 👑

• i2c_master_recv(9)
• i2c_master_send(9)
• i2c_master_send_dmasafe(9)
• struct i2c_device_identity(9)
• enum i2c_driver_flags(9)
• struct i2c_driver(9)
• struct i2c_client(9)
• struct i2c_board_info(9)
• I2C_BOARD_INFO(9)
• struct i2c_algorithm(9)
• struct i2c_lock_operations(9)
• struct i2c_timings(9)
• struct i2c_bus_recovery_info(9)
• struct i2c_adapter_quirks(9)
• i2c_lock_bus(9)
• i2c_trylock_bus(9)
• i2c_unlock_bus(9)
• i2c_mark_adapter_suspended(9)
• i2c_mark_adapter_resumed(9)
• i2c_check_quirks(9)
• module_i2c_driver(9)
• builtin_i2c_driver(9)

---

ngl the dmasafe in the name is literally a promise — if your buffer isn't DMA safe, that's on you and it will not be cute 💀

---

that's the whole page bestie!! 🌸 this one lives in ./include/linux, dated October 2026, and it goes by i2c_master_recv_dmasafe(9) — mwah, go read some kernel source, ily 💜🎀