STRUCT VIRTIO_I2C_REQ(9)
π struct virtio_i2c_req(9) π
okay so bestie, welcome to the Kernel API Manual page for struct virtio_i2c_req, and honestly? she's a little icon and she's about to make so much sense. π
β¨ NAME β¨
struct virtio_i2c_req β literally the virtio I2C request structure. that's her. that's the whole vibe. π¦
β¨ SYNOPSIS β¨
here's the glow-up in code form, no cap, copy it exactly:
struct virtio_i2c_req {
struct completion completion;
struct virtio_i2c_out_hdr out_hdr;
uint8_t *buf;
struct virtio_i2c_in_hdr in_hdr;
};
like... look at those four members. main character energy, all of them. π
β¨ Members β¨
completionβ this is the completion of virtio I2C message. she's the one who tells you when it's done, iykyk. βout_hdrβ the OUT header of the virtio I2C message. the outgoing part, the "hey bestie here's what I need" part. π«Άbufβ the buffer into which data is read, or from which it's written. so like, data goes in, data comes out β she's flexible like that, lowkey iconic. πΈin_hdrβ the IN header of the virtio I2C message. the incoming side of the convo, the reply energy. π
ngl, that's the whole struct. four members, zero drama, maximum slay. π₯
β¨ SEE ALSO β¨
- Kernel file
./drivers/i2c/busses/i2c-virtio.cβ go read the source, it's giving homework but make it cute π struct virtio_i2c(9)β her sibling, also worth a vibe check π
aaaand that's a wrap, bestie!! π this page came to you from ./drivers/i2c/busses, dated October 2026, and yes she's still struct virtio_i2c_req(9) β periodt. π
β¨π¦
π¦ 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