adis_read_reg(9)

📦 version 7.3.1, in nixpkgs unstable

💫 adis_read_reg(9) 💫

okay bestie, welcome to the Kernel API Manual — we're doing a little reading today 🌸 and no, not like book club reading, like reading bytes out of a register reading, which is honestly way more slay.

✨ NAME ✨

adis_read_reg — read N bytes from register 👑

Like. It reads. N bytes. From a register. That's the whole vibe. Short, sweet, iconic, ate and left no crumbs 💅

🦋 SYNOPSIS 🦋

int adis_read_reg (struct adis *adis , unsigned int reg , unsigned int
*val , unsigned int size );

that's the whole signature, copy it exactly bestie, no freestyling ✨

🎀 ARGUMENTS 🎀

  • adis — The adis device 💖 the main character of this whole operation, fr fr.
  • reg — The address of the lower of the two registers 👀 yes, lower, meaning it's giving "there's a higher one too, you're just starting at the bottom" energy.
  • val — The value read back from the device 🫶 this is where the good stuff lands, it's the output, it's the payoff.
  • size — The size of the val buffer 📏 gotta know how much room you've got before you start shoving bytes in there, no cap.

🌈 RETURN 🌈

0 on success ✨ and a negative error code otherwise 😭 — so like, if you see a negative number, that's your sign, sweetie, something went sideways.

🌸 SEE ALSO 🌸

Kernel file ./include/linux/iio/imu/adis.h — plus a whole friend group of functions, and honestly they all ate:

like okay family reunion 💀 literally the entire write squad AND the read squad showed up.

bestie reminder 💜 every single one of those references is listed above, keep them exactly as-is, iykyk.

and that's the page! 🎀 brought to you by ./include/linux/iio/imu, dated October 2026, straight out of the Kernel API Manual — stay hydrated, read your registers responsibly, and remember: 0 means you ate, negative means try again tomorrow 😭✨🫶

📦 where this page comes from