stm32f4_i2c_xfer_msg(9)
π stm32f4_i2c_xfer_msg(9) π
okay so this page comes from the Kernel API Manual, and it's all about transferring one single I2C message β no cap, one message. Let's go, bestie π β¨
πΈ NAME πΈ
stm32f4_i2c_xfer_msg β Transfer a single I2C message
β¨ SYNOPSIS β¨
int stm32f4_i2c_xfer_msg (struct stm32f4_i2c_dev *i2c_dev , struct
i2c_msg *msg , bool is_first , bool is_last );
π ARGUMENTS π
Okay, here's the cast:
i2c_devβ Controller's private data. It's the controller's own little data stash, iykyk.msgβ I2C message to transfer. The message that's getting transferred, periodt.is_firstβ first message of the sequence. It's literally the first one in the sequence, bestie.is_lastβ last message of the sequence. The final one in the sequence. The way that closure hits π«Ά
π¦ SEE ALSO π¦
Kernel file ./drivers/i2c/busses/i2c-stm32f4.c struct stm32f4_i2c_msg(9), 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(9)
Sign-off time: source/version is ./drivers/i2c/busses, and the date is October 2026 β mwah, bestie ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms