st_i2c_xfer_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… st_i2c_xfer_msg(9) β€” like, the whole kernel API manual moment πŸŽ€

okay bestie, welcome to the Kernel API Manual entry for st_i2c_xfer_msg β€” yes it's a section 9 page, yes it's driver-internals core, and yes we're gonna get through it together πŸ’–


✨ NAME ✨

st_i2c_xfer_msg β€” Transfer a single I2C message πŸ¦‹

like, one message. singular. that's the whole vibe. no cap.


🌸 SYNOPSIS 🌸

int st_i2c_xfer_msg (struct st_i2c_dev *i2c_dev , struct i2c_msg *msg ,
bool is_first , bool is_last );

she takes four things and returns an int, periodt πŸ’…


🫢 ARGUMENTS 🫢

  • i2c_dev β€” the controller's private data ✨ like this is her little stash of controller-specific info, ok?
  • msg β€” the I2C message to transfer πŸ“¨ the actual thing being sent out
  • is_first β€” bool, marks this as the first message of the sequence πŸ‘‘ main character energy, opening act
  • is_last β€” bool, marks this as the last message of the sequence 🎬 closing scene, the finale

like the way that is_first and is_last are both bools and both tell you where you are in the sequence?? lowkey iconic. iykyk.


πŸ”₯ SEE ALSO πŸ”₯

okay so this is the part where the manpage flexes its whole friend group 😭 the kernel file ./drivers/i2c/busses/i2c-st.c and, like, every sibling function:

the whole squad fr fr πŸ§šπŸ’œ go read them, they're literally all right there


ngl there's no OPTIONS section, no RETURN VALUE section, no ERRORS, no BUGS, no environment variables, no signals, no exit statuses β€” this page is short and she knows it. don't go looking for stuff that isn't here bestie, i'm not gonna invent it πŸ™ˆ

kisses and bye-bye from ./drivers/i2c/busses, dated October 2026 β€” that's the source and the version and the date all in one cute little sign-off 🌈⭐ slay, go transfer exactly one (1) I2C message πŸ’€πŸ’–

πŸ“¦ where this page comes from