stm32f4_i2c_write_msg(9)
β¨ stm32f4_i2c_write_msg(9) β¨
okay so bestie, welcome to the Kernel API Manual π this one's a little kernel-side function page and honestly it's short and sweet β no cap, it's giving "one job, does it well" energy π
πΈ NAME πΈ
stm32f4_i2c_write_msg β literally just fills the data register in write mode π«Ά that's the whole vibe.
π¦ SYNOPSIS π¦
void stm32f4_i2c_write_msg (struct stm32f4_i2c_dev *i2c_dev );
yep, that's it, that's the whole call. one argument, no return value, in and out π
π ARGUMENTS π
i2c_devβ the controller's private data π this is yourstruct stm32f4_i2c_dev *, the little bundle of state that tells the function which I2C controller we're talking to.
β DESCRIPTION β
so what does it actually do? it fills the data register with the I2C transfer buffer π₯ that's it. that's the function. write mode, data register, buffer goes in. iconic behavior, zero drama π
π§ SEE ALSO π§
the kernel file ./drivers/i2c/busses/i2c-stm32f4.c and its struct β that's where all the lore lives, iykyk πβ¨
and the whole friend group, fr fr:
stm32f4_i2c_msg(9)struct stm32f4_i2c_dev(9)stm32f4_i2c_hw_config(9)stm32f4_i2c_write_byte(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_msg(9)stm32f4_i2c_xfer(9)
go read them, they all ate ππ
heads up bestie: every one of those is a manpage section (9) reference, so likeβ¦ kernel API docs. bring snacks π
and that's the page!! π source lives over in ./drivers/i2c/busses, dated October 2026 β mwah, love that for us, bye 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