__adis_read_reg_32(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __adis_read_reg_32 (9) β€” Kernel API Manual, bestie edition

okay so this is a page from the Kernel API Manual, and it's about __adis_read_reg_32 β€” literally the unlocked version of reading 4 bytes out of a 32-bit register. yes bestie, unlocked, we'll get to that vibe. πŸ¦‹


✨ NAME ✨

__adis_read_reg_32 β€” read 4 bytes from a 32-bit register (unlocked)

like... that's the whole gig. four bytes. 32 bits. no locks involved. periodt. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

int __adis_read_reg_32 (struct adis *adis , unsigned int reg , u32 *val );

three arguments, one int coming back at you. iconic signature ngl ✨


🌸 ARGUMENTS 🌸

  • adis β€” The adis device. it's the device, the main character of this whole function 🫢
  • reg β€” The address of the lower of the two registers. yes, the lower of the two β€” this one's doing a little two-register situation, and you hand it the bottom one. lowkey important detail, don't forget it πŸ’€
  • val β€” The value read back from the device. this is where the goods land, so make sure it's a real u32 * and not some nonsense πŸ“

⭐ RETURN ⭐

0 on success, a negative error code otherwise. that's it, that's the whole return contract β€” zero means slay, anything negative means something went sideways 😭


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./include/linux/iio/imu/adis.h, plus the whole friend group:

ngl that's a stacked SEE ALSO section, iykyk πŸ‘‘


heads up bestie: this is the unlocked one β€” the double-underscore at the front is the whole tell. if you're reaching for the version that handles locking for you, that's a different function in the list above, so vibe check which one you're actually calling before you commit πŸ™ˆ

and that's the page!! brought to you by the source at ./include/linux/iio/imu, dated October 2026, filed under __adis_read_reg_32(9) β€” go read your registers responsibly, ily, bye πŸ’–πŸ§šβ€β™€οΈπŸŒˆ

πŸ“¦ where this page comes from