STRUCT VIRTIO_I2C_REQ(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ 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