iio_backend_ext_info_set(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to the Kernel API Manual page for iio_backend_ext_info_set β€” it's the IIO ext_info write callback and honestly it's giving "quiet helper that does the important thing." πŸ’…


✨ SYNOPSIS ✨

ssize_t iio_backend_ext_info_set (struct iio_dev *indio_dev , uintptr_t
       private , const struct iio_chan_spec *chan , const char *buf , size_t
       len );
copy that signature exactly bestie, no creative editing, I'm begging πŸ™ˆ

🫢 ARGUMENTS 🫢

  • indio_dev β€” the IIO device. the main character, lowkey.
  • private β€” data that's private to the driver. not for sharing, it's on a need-to-know basis πŸ’œ
  • chan β€” the IIO channel. the lil lane your data travels on.
  • buf β€” the buffer holding the sysfs attribute. this is where the text actually lives πŸŽ€
  • len β€” the length of that buffer. numbers matter, periodt.

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: this helper is intended to be used by backends that extend an IIO channel β€” you do that through iio_backend_extend_chan_spec β€” and add extended info while you're at it. ✨

in that situation, backends are not supposed to give their own callbacks. why? because they would not have a way to get the backend from indio_dev. like, no path home. no cap. 😭

and this one? this is the setter. the one that writes. the queen of the pair, iykyk πŸ‘‘


πŸ’€ RETURN πŸ’€

  • Buffer length on success πŸŽ‰
  • a negative error number on failure 😭

that's it, that's the whole mood. no in-between, no "it depends."


πŸ”₯ SEE ALSO πŸ”₯

first up, the actual kernel file, go read it:

  • ./drivers/iio/industrialio-backend.c

and now the whole squad, everybody say hi πŸ‘‹:


okay that's the page!! πŸŽ€ this lovely thing lives down in ./drivers/iio and it's dated October 2026 β€” so go forth, write your ext_info, and slay. mwah πŸ’–πŸ’…βœ¨

πŸ“¦ where this page comes from