octeon_i2c_read(9)

💅 octeon_i2c_read — Kernel API Manual, bestie edition 💅

okay so you're in the Kernel API Manual and the function on the menu today is octeon_i2c_read — it's giving "receive data from the bus via low-level controller" energy, and honestly? iconic. Let's get into it. 🦋

---

✨ NAME ✨

octeon_i2c_read — receive data from the bus via low-level controller 🌸

literally what it says: you want bytes off the bus, this is the low-level controller way to get them. no cap.

---

🎀 SYNOPSIS 🎀

int octeon_i2c_read (struct octeon_i2c *i2c , int target , u8 *data ,
u16 *rlength , bool recv_len );

five arguments, returns an int, slay. 💅

---

🔥 ARGUMENTS 🔥

• i2c — The struct octeon_i2c. that's your controller bestie, the whole struct, hand it over 🫶
• target — Target address. who we talkin' to on the bus 👑
• data — Pointer to the location to store the data. this is where the good stuff lands ✨
• rlength — Length of the data. it's a u16 *, so pointer, not a plain number, keep that in mind 💜
• recv_len — flag for length byte. a bool, and yeah it's the flag that says we're doing the length byte thing 🙈

---

🌈 DESCRIPTION 🌈

The address is sent over the bus, then the data is read. that's the whole vibe check, fr fr — first the address goes out, then the read happens. 🎯

---

⭐ RETURN ⭐

0 on success, otherwise a negative errno. so like, zero means we ate, negative means something went sideways 😭

---

💖 SEE ALSO 💖

Kernel file ./drivers/i2c/busses/i2c-octeon-core.c — plus the whole friend group:

• octeon_i2c_wait(9)
• octeon_i2c_hlc_wait(9)
• octeon_i2c_start(9)
• octeon_i2c_write(9)
• octeon_i2c_hlc_block_comp_read(9)
• octeon_i2c_hlc_block_comp_write(9)
• octeon_i2c_xfer(9)

go read them too, iykyk 🧚

---

ok and for the receipts: this page lives under ./drivers/i2c/busses and it's dated October 2026. 💀

and that's the whole page bestie — stay hydrated, read your errno values, and remember: negative means no 💔 mwah 🍓✨