ads112c14_i2c_read_bytes(9)

💖 ads112c14_i2c_read_bytes — the Kernel API Manual moment 💖

okay so bestie, we're in the kernel API manual (that's the manual name, bestie, it's literally right there in the header) and this page is all about one function: ads112c14_i2c_read_bytes. It's giving "read bytes off the device over I2C" and honestly? iconic.

---

✨ NAME ✨

ads112c14_i2c_read_bytes — Read bytes from the device over I2C 🦋

---

🌸 SYNOPSIS 🌸

int ads112c14_i2c_read_bytes (struct i2c_client *client , u8 cmd , u8
*buf , u8 len , bool use_crc );

no cap, that's the whole signature, copy it exactly bestie 💅

---

🎀 ARGUMENTS 🎀

• client — the I2C client for the device 🫶 like, who we're talking to, basically.
• cmd — the command we send to the device before reading. yes, before. we're polite like that ✨
• buf — the buffer where the read bytes get stashed. your little byte hotel 🏨
• len — how many bytes to read. the count, the vibe check, the amount 🌈
• use_crc — whether to use CRC8 for the data integrity check. true = we're checking, false = we're living dangerously (jk, it's just off) 💀

---

💜 DESCRIPTION 💜

It's lowkey simple: if I2C_CRC is enabled, you can set use_crc to true and it'll perform a CRC8 check on the received data. that's the whole tea ☕✨

fr fr though — that CRC8 check only happens when I2C_CRC is enabled, so don't go thinking use_crc = true does anything magical if it isn't. the manpage said what it said 💅

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/iio/adc/ti-ads112c14.c 👑
• ads112c14_regmap_bus_read(9) — read bestie energy
• ads112c14_regmap_bus_write(9) — write bestie energy

---

okay that's the whole page, mwah 💋 and for the cute sign-off: this beauty lives under ./drivers/iio/adc, dated October 2026 — main character source-and-version energy, periodt 🌟🎀