STRUCT SSP_DATA(9)

🎀 struct ssp_data(9) — like, the ssp platformdata structure, bestie 🎀

okay so this is a page from the Kernel API Manual and honestly? it's kind of a whole vibe. sit down, grab a strawberry drink 🍓, and let's get into struct ssp_data — the ssp platformdata structure itself. no cap, it's a big one.

---

✨ NAME ✨

struct ssp_data — ssp platformdata structure 💖

---

🌸 SYNOPSIS 🌸

okay so picture this — the whole struct, exactly as it lives:

struct ssp_data {
    struct spi_device *spi;
    const struct ssp_sensorhub_info *sensorhub_info;
    struct timer_list wdt_timer;
    struct work_struct work_wdt;
    struct delayed_work work_refresh;
    bool shut_down;
    bool mcu_dump_mode;
    bool time_syncing;
    int64_t timestamp;
    int check_status[SSP_SENSOR_MAX];
    unsigned int com_fail_cnt;
    unsigned int reset_cnt;
    unsigned int timeout_cnt;
    unsigned int available_sensors;
    unsigned int cur_firm_rev;
    char last_resume_state;
    char last_ap_state;
    unsigned int sensor_enable;
    u32 delay_buf[SSP_SENSOR_MAX];
    s32 batch_latency_buf[SSP_SENSOR_MAX];
    s8 batch_opt_buf[SSP_SENSOR_MAX];
    int accel_position;
    int mag_position;
    int fw_dl_state;
    struct mutex comm_lock;
    struct mutex pending_lock;
    struct gpio_desc *mcu_reset_gpiod;
    struct gpio_desc *ap_mcu_gpiod;
    struct gpio_desc *mcu_ap_gpiod;
    struct list_head pending_list;
    struct iio_dev *sensor_devs[SSP_SENSOR_MAX];
    atomic_t enable_refcount;
    __le16 header_buffer[SSP_HEADER_BUFFER_SIZE / sizeof(__le16)];
};

like, she's serving structure. periodt. 👑

---

💅 MEMBERS 💅

every single field, bestie, in order, no skips — here we go 🫶

• spi — the spi device. that's her.
• sensorhub_info — info about sensorhub board specific features 🌈
• wdt_timer — watchdog timer ⏰
• work_wdt — watchdog work
• work_refresh — refresh work queue for reset request from MCU. she refreshes. iconic.
• shut_down — shut down flag
• mcu_dump_mode — mcu dump mode for debug 🔥
• time_syncing — time syncing indication flag
• timestamp — previous time in ns calculated for time syncing (nanoseconds, not vibes)
• check_status — status table for each sensor
• com_fail_cnt — communication fail count 😭 (we've all been there)
• reset_cnt — reset count
• timeout_cnt — timeout count
• available_sensors — available sensors seen by sensorhub (bit array)
• cur_firm_rev — cached current firmware revision
• last_resume_state — last AP resume/suspend state used to handle the PM state of ssp
• last_ap_state — (obsolete) sleep notification for MCU. lowkey legacy, but she's still here 💀
• sensor_enable — sensor enable mask
• delay_buf — data acquisition intervals table
• batch_latency_buf — yet unknown but existing in communication protocol 🙈
• batch_opt_buf — yet unknown but existing in communication protocol
• accel_position — yet unknown but existing in communication protocol
• mag_position — yet unknown but existing in communication protocol
• fw_dl_state — firmware download state
• comm_lock — lock protecting the handshake 🤝
• pending_lock — lock protecting pending list and completion
• mcu_reset_gpiod — mcu reset line
• ap_mcu_gpiod — ap to mcu gpio line
• mcu_ap_gpiod — mcu to ap gpio line
• pending_list — pending list for messages queued to be sent/read
• sensor_devs — registered IIO devices table 🎀
• enable_refcount — enable reference count for wdt (watchdog timer)
• header_buffer — cache aligned buffer for packet header ✨

ngl the four "yet unknown but existing in communication protocol" fields are giving mystery main character energy — they're literally in the struct, they're literally undocumented beyond existing, and we respect them for it 🦋

---

👑 SEE ALSO 👑

• Kernel file ./drivers/iio/common/ssp_sensors/ssp.h — go read the source, iykyk 💜

---

and that's the whole page, bestie!! remember: this was the Kernel API Manual, struct ssp_data(9), from ./drivers/iio/common/ssp_sensors, dated October 2026. slay, go forth, and read your headers 🌟💖🎀