stm32f4_i2c_xfer_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ 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