STRUCT AD5360_STATE(9)

💖 NAME 💖

Okay so this page comes from the Kernel API Manual, and the main character is struct ad5360_state — that’s the driver instance specific data, no cap. It’s the struct that holds one driver instance’s specific data, and we’re gonna vibe-check every member. Periodt. 🫶

✨ SYNOPSIS ✨

struct ad5360_state {
    struct spi_device               *spi;
    const struct ad5360_chip_info   *chip_info;
    struct regulator_bulk_data      vref_reg[3];
    unsigned int                    ctrl;
    struct mutex                    lock;
    union {
      __be32 d32;
      u8 d8[4];
    } data[2];
};

🌸 Members 🌸

• spi — the spi_device, bestie. That’s the SPI device member, exactly as the struct says.
• chip_info — chip model specific constants, available modes etc. All that model-specific lore lives here, iykyk.
• vref_reg — vref supply regulators. Yep, the vref supply regulators, iconic.
• ctrl — control register cache. It’s giving “cache the control register,” periodt.
• lock — lock to protect the data buffer during SPI ops. Do not sleep on this one: its whole job is protecting the data buffer during SPI ops.
• data — spi transfer buffers. The SPI transfer buffers, fr fr.

👀 SEE ALSO 👀

• Kernel file ./drivers/iio/dac/ad5360.c
• struct ad5360_chip_info(9)

Go read those if you want the full lore, bestie. 💅

Cute sign-off: source/version ./drivers/iio/dac, dated October 2026, page struct ad5360_state(9) — bye bestie, slay! ✨💖