octeon_i2c_...k_comp_write(9)

🌸 NAME 🌸

okay so this is the Kernel API Manual page for octeon_i2c_hlc_block_comp_write — the page title is octeon_i2c_...k_comp_write(9) — and it's literally the high-level-controller composite block write situation. the full name vibe is octeon_i2c_hlc_block_comp_write - high-level-controller composite block write. long name, main character energy, we love her 💅

✨ SYNOPSIS ✨

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

🎀 ARGUMENTS 🎀

• i2c — the struct octeon_i2c. yes bestie, that's the whole assigned role 🫶
• msgs — msg[0] contains address, msg[1] contains data to be written. that's the split, no cap 😌

🦋 DESCRIPTION 🦋

so the i2c core command is constructed, and the write data gets written into the FIFO buffer. executing that command will result in a HW write, using the data in FIFO. it's the move for when the i2c xfer is for greater than 8 bytes of write data. literally built for the bigger-write moment ✨

💖 RETURN 💖

0 on success, otherwise a negative errno. slay when it's zero, sad little negative errno when it's not 😭

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/i2c/busses/i2c-octeon-core.c
• octeon_i2c_wait(9)
• octeon_i2c_hlc_wait(9)
• octeon_i2c_start(9)
• octeon_i2c_read(9)
• octeon_i2c_write(9)
• octeon_i2c_hlc_block_comp_read(9)
• octeon_i2c_xfer(9)

xoxo bestie 💖 source/version: ./drivers/i2c/busses; date: October 2026. go read the kernel file, iykyk 🧚‍♀️