STRUCT STM32F4_I2C_MSG(9)

✨ NAME ✨

okay so bestie, this is struct stm32f4_i2c_msg(9) from the Kernel API Manual, and the vibe is literally: struct stm32f4_i2c_msg — client specific data. no cap, that’s the whole name bit 💅

🌈 SYNOPSIS 🌈

here’s the struct in all its main-character glory:

       struct stm32f4_i2c_msg {
           u8 addr;
           u32 count;
           u8 *buf;
           int result;
           bool stop;
        };

🫶 Members 🫶

• addr — the 8-bit target addr, including the r/w bit. yes, r/w is in there too, bestie ✨
• count — number of bytes to be transferred 🎀
• buf — data buffer 💖
• result — result of the transfer 👑
• stop — last I2C msg to be sent, i.e. STOP to be generated 🔥

👑 SEE ALSO 👑

• Kernel file ./drivers/i2c/busses/i2c-stm32f4.c struct stm32f4_i2c_dev(9), stm32f4_i2c_hw_config(9), stm32f4_i2c_write_byte(9), stm32f4_i2c_write_msg(9), stm32f4_i2c_handle_write(9), stm32f4_i2c_handle_read(9), stm32f4_i2c_handle_rx_done(9), stm32f4_i2c_handle_rx_addr(9), stm32f4_i2c_isr_event(9), stm32f4_i2c_isr_error(9), stm32f4_i2c_xfer_msg(9), stm32f4_i2c_xfer(9) — go read these too, iykyk 🦋

ok bye bestie 🫶 this page lives under ./drivers/i2c/busses, it’s dated October 2026, and it’s literally the struct stm32f4_i2c_msg(9) page 💅✨