cros_ec_sen...ore_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cros_ec_sen...ore_register β€” Kernel API Manual ✨

okay so bestie, buckle up, because this is the full name: cros_ec_sensors_core_register πŸ¦‹. It's a kernel API manual page, and no, the truncated title in the header isn't a glitch, that's just how the page name got cut off, iykyk.


🌸 NAME 🌸

cros_ec_sensors_core_register β€” register a callback to FIFO and IIO when the sensor is ready. The way this one works: you have to call it at the very end of the sensor probe routine. Like, the end end. Periodt. πŸ’…


✨ SYNOPSIS ✨

int cros_ec_sensors_core_register (struct device *dev , struct iio_dev
*indio_dev , cros_ec_sensorhub_push_data_cb_t push_data );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device that got created for the sensor, bestie. It's giving "who am I" energy. 🫢
  • indio_dev β€” the iio device structure of the device. Yes, that's literally what it is, no notes. πŸ’–
  • push_data β€” the function you hand over, and it gets called when cros_ec_sensorhub receives a sample for that sensor. So basically your callback gets pinged whenever there's tea to spill. πŸ”₯

πŸ”₯ RETURN πŸ”₯

0 on success, -errno on failure. That's it, that's the whole vibe check. 😭

ngl if you're getting a -errno back, something did not slay. Check your args, bestie.

πŸ¦‹ SEE ALSO πŸ¦‹


okay that's the whole page, bestie, you're officially educated πŸ’œ. This lil masterpiece lives at ./drivers/iio/common/cros_ec_s... and it's dated October 2026, and the header/footer keeps saying cros_ec_sen...ore_register(9) because truncation is just her main character trait. mwah πŸŽ€βœ¨

πŸ“¦ where this page comes from