st_i2c_xfer(9)

✨ st_i2c_xfer(9) — the Kernel API Manual, bestie edition ✨

okay so this is st_i2c_xfer from the Linux Kernel API Manual and it's literally the function that sends one single I2C message out into the world 💅 like it's giving "just one message" energy and honestly? iconic.

---

🌸 NAME 🌸

st_i2c_xfer — Transfer a single I2C message 🦋

---

💖 SYNOPSIS 💖

int st_i2c_xfer (struct i2c_adapter *i2c_adap , struct i2c_msg msgs[] ,
       int num );

no cap, that's the whole signature ✨

---

🎀 ARGUMENTS 🎀

• i2c_adap — Adapter pointer to the controller 💫 like this is your little handle to the controller itself
• msgs — Pointer to data to be written ✍️ yes bestie, the actual data lives over here
• num — Number of messages to be executed 🔢 how many we're running, periodt

---

🫶 SEE ALSO 🫶

Kernel file ./drivers/i2c/busses/i2c-st.c and its whole friend group 🌈:

• struct st_i2c_timings(9)
• struct st_i2c_client(9)
• struct st_i2c_dev(9)
• st_i2c_hw_config(9)
• st_i2c_write_tx_fifo(9)
• st_i2c_wr_fill_tx_fifo(9)
• st_i2c_rd_fill_tx_fifo(9)
• st_i2c_terminate_xfer(9)
• st_i2c_handle_write(9)
• st_i2c_handle_read(9)
• st_i2c_isr_thread(9)
• st_i2c_xfer_msg(9)

the way that list just goes on and on 😭 but every single one is a main character, iykyk 💜

---

heads up bestie 🙈 the source path on that SEE ALSO line is ./drivers/i2c/busses and that's where all this lives — don't go looking anywhere else 💀

---

✨ cute little sign-off ✨ — this page comes from the ./drivers/i2c/busses source, st_i2c_xfer(9), dated October 2026 🎀 that's a wrap, ily, go transfer some messages 🦋💖