STRUCT CROS_EC_SENSORS_CORE_STATE(9)

💅 struct cros_ec_sensors_core_state(9) — the Kernel API Manual glow-up

okay so picture this: it's a big ol' C struct living in the Kernel API Manual, section 9, and its whole personality is "state data for EC sensors IIO driver". that's it, that's the job. and honestly? it ate. let's get into it 🫶

---

✨ NAME ✨

struct cros_ec_sensors_core_state — literally just the state data for the EC sensors IIO driver. main character energy for a struct, ngl 💅

---

🌸 SYNOPSIS 🌸

here's the whole shape of her, exactly as she is, no edits bestie:

struct cros_ec_sensors_core_state {
    struct cros_ec_device *ec;
    struct mutex cmd_lock;
    struct cros_ec_command *msg;
    struct ec_params_motion_sense param;
    struct ec_response_motion_sense *resp;
    enum motionsensor_type type;
    bool range_updated;
    int curr_range;
    struct calib_data {
      s16 offset;
      u16 scale;
    } calib[CROS_EC_SENSOR_MAX_AXIS];
    s8 sign[CROS_EC_SENSOR_MAX_AXIS];
    u8 samples[CROS_EC_SAMPLE_SIZE];
    int (*read_ec_sensors_data)(struct iio_dev *indio_dev, unsigned long
scan_mask, s16 *data);
    u32 fifo_max_event_count;
    int frequencies[6];
 };

like… she's serving structure. the nested struct calib_data in there? iconic. ✨

---

🎀 Members 🎀

breaking down every single member because we do NOT skip:

• ec — the cros EC device structure. yeah, the whole device. she's holding the keys 🔑
• cmd_lock — a struct mutex lock that stops simultaneous access to the commands. no cutting the line, no double-dipping, periodt 💀
• msg — the cros EC command structure 🎯
• param — motion sensor parameters structure, the input side of the convo
• resp — motion sensor response structure, the reply side. it's giving call and response 🦋
• type — type of motion sensor (enum motionsensor_type, if you were curious 👀)
• range_updated — True if the range of the sensor has been updated. she keeps receipts 📝
• curr_range — if updated, the current range value. and bestie, listen: it gets reapplied at every resume. every single one. commitment 💖
• calib — the calibration parameters. quick note that matters: trigger captured data will always provide the calibrated data. so like, don't worry about it, it's already handled 🌈
• samples — a static array holding data from a single capture. for each channel we need 2 bytes, except for the timestamp — the timestamp is always last and is always 8-byte aligned. alignment is self-care, fr fr ✨
• read_ec_sensors_data — the function used for accessing sensors values. the lil worker bee 🐝
• fifo_max_event_count — size of the EC sensor FIFO 📦
• frequencies — table of known available frequencies: 0, Min and Max in mHz 🎵

ngl the members list above is exactly what the page gives us — no more, no less. if you're looking for the tea on sign, that's not spilled here 🙈

---

🔥 SEE ALSO 🔥

• Kernel file ./include/linux/iio/common/cros_ec_sensors_core.h — go read her, iykyk 📖

---

and that's the whole vibe check, bestie 💜 this little gem comes to you from ./include/linux/iio/common, dated October 2026, and it's filed under struct cros...s_core_state(9) in the Kernel API Manual. slay, stay hydrated, and always align your timestamps 🎀✨🦋