cros_ec_sen...e_read_avail(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cros_ec_sen...e_read_avail(9)

okay so bestie, welcome to the Kernel API Manual ✨ — yes the title up top is cros_ec_sen...e_read_avail(9) (the kernel just loves truncating things, we don't question it 💀). This one's all about pulling the list of values a sensor channel can actually report. Let's get into it 🫶

🌸 NAME 🌸

cros_ec_sensors_core_read_avail — get available values 💖

✨ SYNOPSIS ✨

int cros_ec_sensors_core_read_avail (struct iio_dev *indio_dev , struct
       iio_chan_spec const *chan , const int **vals , int *type , int *length ,
       long mask );

🎀 ARGUMENTS 🎀

  • indio_dev — the pointer to the state information for the device, iykyk 🌈
  • chan — the channel specification structure table, main character energy fr
  • vals — the list of available values 👑
  • type — the type of data returned
  • length — the number of data returned in the array
  • mask — specifies which values to be requested (yes a mask, we love a mask) 🙈

🔥 RETURN 🔥

So what comes back? Either an error code, or one of:

  • IIO_AVAIL_RANGE
  • IIO_AVAIL_LIST

like, those are the two (2) good outcomes, periodt 💅

🦋 SEE ALSO 🦋

The kernel file lives right here, no cap:

./drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core.c

and it's giving whole friend group — go say hi to:

k that's the whole thing bestie, go forth and read those avail values 💜 — this page came from ./drivers/iio/common/cros_ec_s... and is dated October 2026 ⭐ (yes, the source and the date are also being dramatic and truncated, slay). mwah, bye 🍓🧚

📦 where this page comes from