octeon_i2c_h...ck_comp_read(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 octeon_i2c_hlc_block_comp_read(9) 🌸

okay bestie, welcome to the Kernel API Manual ✨ — yes, the Linux kernel has man pages too, and this one is a whole little vibe. today we're looking at octeon_i2c_hlc_block_comp_read. it's giving "niche but iconic" 💅

🎀 NAME 🎀

octeon_i2c_hlc_block_comp_read — the high-level-controller composite block read ✨ lowkey a mouthful but she's doing her thing

🦋 SYNOPSIS 🦋

int octeon_i2c_hlc_block_comp_read (struct octeon_i2c *i2c , struct i2c_msg *msgs );

like, that's the whole signature. no cap. 🫶

💖 ARGUMENTS 💖

  • i2c — the struct octeon_i2c, that's her whole personality tbh. she holds the state 🌈
  • msgs — bestie, listen: msg[0] contains the address, and you place read data into msg[1]. that's the deal. msg zero is the address-carrier, msg one is the data-receiver 📥

👑 DESCRIPTION 👑

okay so here's the lore 🧚

the i2c core command is constructed and written into the SW_TWSI register. that's step one, main character energy.

the execution of the command will result in requested data being placed into a FIFO buffer, ready to be read. yes, FIFO. first in, first out. queue girlies stay winning 🍓

and the whole reason she exists? she's used in the case where the i2c xfer is for greater than 8 bytes of read data. that's her moment. that's her whole arc. anything chunky, she handles it 🔥

⭐ RETURN ⭐

  • 0 on success 🥳
  • otherwise a negative errno 😭 (it's fine, it's fine, check the errno, you got this)

🦋 SEE ALSO 🦋

kernel file ./drivers/i2c/busses/i2c-octeon-core.c — go read her neighbors, they're all linked up like a group chat fr fr:

ngl she's a kernel-internal helper, so no shell commands to run here — this one's for the driver devs and the i2c girlies specifically. iykyk 💅

that's the whole page bestie, you ate that reading 🫶 — this little manual lives at ./drivers/i2c/busses, dated October 2026, and honestly? iconic of her. periodt. 💖✨🎀

📦 where this page comes from