rk3x_i2c_fill_transmit_buf(9)

🌸 rk3x_i2c_fill_transmit_buf — NAME energy 🌸

okay so bestie, welcome to the rk3x_i2c_fill_transmit_buf(9) page from the Kernel API Manual — yes that's the manual name, we're being official today 💅

Here's the whole vibe: rk3x_i2c_fill_transmit_buf fills the transmit buffer with data from i2c->msg. That's it, that's the function. It takes the stuff sitting in i2c->msg and yeets it into the transmit buffer. Iconic, honestly ✨

🎀 SYNOPSIS 🎀

void rk3x_i2c_fill_transmit_buf (struct rk3x_i2c *i2c );

yup, returns void, takes exactly one pointer, no extra drama 🫶

🦋 ARGUMENTS 🦋

• i2c — the target controller data 💖 that's your struct rk3x_i2c * and it's literally the whole personality of this call

👑 SEE ALSO 👑

the whole friend group, no gatekeeping 🔥 — and yeah, these all live in the kernel file ./drivers/i2c/busses/i2c-rk3x.c:

• struct i2c_spec_values(9)
• struct rk3x_i2c_calced_timings(9)
• struct rk3x_i2c_soc_data(9)
• struct rk3x_i2c(9)
• rk3x_i2c_start(9)
• rk3x_i2c_stop(9)
• rk3x_i2c_prepare_read(9)
• rk3x_i2c_get_spec(9)
• rk3x_i2c_v0_calc_timings(9)
• rk3x_i2c_v1_calc_timings(9)
• rk3x_i2c_clk_notifier_cb(9)
• rk3x_i2c_setup(9)

ngl bestie, that's the entire page — short and sweet, main character energy only 💀 but like, go read the friends above if you want the full lore, iykyk 🌈

and that's a wrap, mwah 💋 this cutie came from ./drivers/i2c/busses, dated October 2026, and it goes by rk3x_i2c_fill_transmit_buf(9) — periodt 🍓🧚💜