STRUCT LOONGSON2_I2C_MSG(9)
π struct loongson2_i2c_msg(9) π
okay so bestie, welcome to the kernel API manual page for struct loongson2_i2c_msg(9) β yes that's the whole header vibe, we're folding it in up top so nobody loses the plot π
β¨ NAME β¨
struct loongson2_i2c_msg β client specific data, and honestly? that's it, that's the whole personality π
πΈ SYNOPSIS πΈ
struct loongson2_i2c_msg {
u8 *buf;
u32 count;
int result;
u8 addr;
bool stop;
};
look at her. five fields. immaculate. no notes. π«Ά
π¦ Members π¦
bufβ data buffer, the actual bytes doing the work, main character energy fr fr π«countβ number of bytes to be transferred, like how much we're shipping out, no cap π¦resultβ result of the transfer, the vibe check after the fact β did it slay or did it flop πaddrβ 8-bit slave addr, including r/w bit, so the address and the read/write intent are packed in together, iykyk π₯stopβ last I2C msg to be sent, i.e. STOP to be generated, so setting this means "okay we're done here, generate the STOP" periodt βπ
β SEE ALSO β
- Kernel file
./drivers/i2c/busses/i2c-ls2x-v2.cstructloongson2_i2c_priv(9)β go read her big sister next, she's iconic too π
ngl, if you're poking at these fields directly you're probably deep in a driver and that's very demure, very mindful of you π
and that's a wrap bestie!! this lil page lives in ./drivers/i2c/busses, dated October 2026, and it's officially titled struct loongson2_i2c_msg(9) β go forth and transfer those bytes π
β¨πΈ
π¦ 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