STRUCT AD5764_STATE(9)

💅 struct ad5764_state(9) — the whole vibe

okay so bestie, welcome to the kernel API manual, and today's main character is struct ad5764_state — literally the driver instance specific data 🫶 like it's the little bag of stuff one specific AD5764 driver instance carries around with it, and honestly? iconic.

---

✨ NAME ✨

struct ad5764_state — driver instance specific data 🎀

No cap, that's the whole job description: it's the per-instance state blob, one of these per driver instance, and everything it needs lives in here.

---

🌸 SYNOPSIS 🌸

Look at her. Perfection. Copy it exactly, don't you dare touch a character 💅

struct ad5764_state {
    struct spi_device               *spi;
    const struct ad5764_chip_info   *chip_info;
    struct regulator_bulk_data      vref_reg[2];
    struct mutex                    lock;
    union {
      __be32 d32;
      u8 d8[4];
    } data[2];
 };

---

🦋 Members 🦋

• spi — a spi_device, bestie. The SPI device, right there in the struct, living her best life 🫶
• chip_info — chip info ✨ that's it, that's the description, and honestly she ate.
• vref_reg — vref supply regulators 🌈 the supply regulators for vref. Plural energy, we love to see it.
• lock — lock to protect the data buffer during SPI ops 🔥 this is the security guard for the data buffer while SPI operations are happening. respect her.
• data — spi transfer buffers 🎀 the buffers where the SPI transfers actually go down.

---

👑 SEE ALSO 👑

• Kernel file ./drivers/iio/dac/ad5764.c — go read the actual driver, iykyk 💜
• struct ad5764_chip_info(9) — her bestie, her ride-or-die, the chip info struct 💖

---

ok real talk, quick vibe check: these are the members and the references, and that's genuinely everything this page gives you. no extra lore, no hidden flags. periodt 💅

---

⭐ and that's the page!! this one comes from ./drivers/iio/dac, dated October 2026, and it's struct ad5764_state(9) all the way down 🧚 mwah, go forth and slay your SPI ops 💖🌸