STRUCT EC_I2C_DEVICE(9)

💜 struct ec_i2c_device(9) — the Kernel API Manual glow-up

okay bestie, so this is a page from the Kernel API Manual about struct ec_i2c_device(9), and honestly? it's giving "small struct, big responsibilities" energy. let's get into it ✨

---

🌸 NAME 🌸

struct ec_i2c_device — literally the driver data for the I2C tunnel 🚇 no cap, that's the whole vibe.

---

✨ SYNOPSIS ✨

struct ec_i2c_device {
    struct device *dev;
    struct i2c_adapter adap;
    struct cros_ec_device *ec;
    u16 remote_bus;
    u8 request_buf[256];
    u8 response_buf[256];
 };

like, look at her. five fields and two chonky buffers. icon behavior 💅

---

🎀 Members 🎀

• dev — the device node 🫶 that's her home address basically.
• adap — the I2C adapter. the actual machinery, the main character of the bus world 👑
• ec — a pointer to the EC device 🧚 that's who we're talking to on the other side.
• remote_bus — the EC bus number we tunnel to on the other side 🌈 like, the far-away bus we're reaching through the tunnel. it's a u16, noted.
• request_buf — buffer for transmitting data 📤 and fr fr, we expect most transfers to fit. it's u8 request_buf[256] — 256 bytes of sending space, bestie.
• response_buf — buffer for receiving data 📥 same deal, we expect most transfers to fit. u8 response_buf[256], 256 bytes of incoming room. it's giving symmetry 💖

ngl the "we expect most transfers to fit" is doing a lot of heavy lifting in both of those descriptions. just saying. 😭

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/i2c/busses/i2c-cros-ec-tunnel.c — yes, the actual source, go read it, iykyk 📖
• ec_i2c_count_message(9)
• ec_i2c_construct_message(9)
• ec_i2c_count_response(9)
• ec_i2c_parse_response(9)

the whole lil friend group, all together, slay 🫶

---

and that's the page, bestie!! this one came from ./drivers/i2c/busses and it's dated October 2026 — so like, go off, future manpage 💀✨ mwah, see you in the next man page 💜🎀