STRUCT YAS5XX_CHIP_INFO(9)

✨ NAME ✨

struct yas5xx_chip_info — device-specific data and function pointers, bestie 💅

So this is from the Kernel API Manual (yes, the whole manual, not just a vibe), and it's literally the little info card that tells the driver everything it needs to know about each YAS chip. Obsessed.

---

🌸 SYNOPSIS 🌸

struct yas5xx_chip_info {
    unsigned int devid;
    const char *product_label;
    const char *product_name;
    const char *version_names[2];
    const int *volatile_reg;
    int volatile_reg_qty;
    u32 scaling_val2;
    u16 t_ref;
    s16 min_temp_x10;
    int (*get_measure)(struct yas5xx *yas5xx, s32 *to, s32 *xo, s32 *yo,
s32 *zo);
    int (*get_calibration_data)(struct yas5xx *yas5xx);
    void (*dump_calibration)(struct yas5xx *yas5xx);
    int (*measure_offsets)(struct yas5xx *yas5xx);
    int (*power_on)(struct yas5xx *yas5xx);
 };

---

🎀 Members 🎀

Okay so here's the whole cast — every single one of them, no skips, periodt:

• devid — the device ID number. Like the chip's little student ID 🪪
• product_label — the product label used in Linux. It's giving official paperwork ✨
• product_name — the product name of the YAS variant. Which flavour of YAS are we dealing with, iykyk 🌈
• version_names — the version letters or namings. Cute little name tags for each version 🎀
• volatile_reg — device-specific volatile registers. Handle with care, they're spicy 🔥
• volatile_reg_qty — quantity of device-specific volatile registers. Just counting the spicy ones 💀
• scaling_val2 — scaling value for IIO_CHAN_INFO_SCALE. Math but make it fashion 💅
• t_ref — number of counts at reference temperature 20 °C. Twenty degrees, iconic 🌡️
• min_temp_x10 — starting point of temperature counting in 1/10:s degrees Celsius. Yes, tenths, don't @ me 🧊
• get_measure — function pointer to get a measurement. Go get that data, bestie 🫶
• get_calibration_data — function pointer to get calibration data. The calibration lore is real 📖
• dump_calibration — function pointer to dump calibration for debugging. Debug girlies rise 🙈
• measure_offsets — function pointer to measure the offsets. Offsets getting measured fr fr 📐
• power_on — function pointer to power-on procedure. Wake up, chip, we're going to the club ⚡

---

💖 Description 💖

Okay so real talk — the t_ref value for YAS532/533 is known from the Android driver. For YAS530 and YAS537 it was approximately measured. Approximately! So if you're wondering where those numbers came from, now you know 💀

And the temperatures min_temp_x10 are derived from the temperature resolutions given in the data sheets. That's it, that's the tea ☕

Ngl these numbers aren't just vibes — they have sources, but some sources are "the Android driver" and some are "we measured it approximately", and that's just how it is.

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/iio/magnetometer/yamaha-yas530.c struct yas5xx(9)
• yas530_measure(9)
• yas537_measure(9)
• yas530_get_measure(9)
• yas537_get_measure(9)
• yas530_extract_calibration(9)

---

Go read those, bestie, they're all part of the same little magnetometer friend group 🧲💖

Kiss kiss, this page lives at ./drivers/iio/magnetometer, dated October 2026 — slay, you found the whole thing, periodt ✨🎀