STRUCT AD5064_CHIP_INFO(9)

✨ NAME ✨

struct ad5064_chip_info — the lil info card that tells you what a specific chip is like 💅

So basically, this system is the Kernel API Manual bestie, and every chip gets its own little personality sheet. Let's get into it 🫶

🎀 SYNOPSIS 🎀

struct ad5064_chip_info {
    bool shared_vref;
    unsigned long internal_vref;
    const struct iio_chan_spec *channels;
    unsigned int num_channels;
    enum ad5064_regmap_type regmap_type;
 };

Like, that's the whole struct, no cap. Five fields, all of them important, none of them filler 💖

💅 MEMBERS 💅

• shared_vref — a bool that answers the question "is the vref supply shared between the channels?" Like, do all the channels have to share one vibe or does each one get its own ✨
• internal_vref — an unsigned long holding the internal reference voltage. And listen: it's 0 if the chip has no internal vref. Zero means "nope, not here", not "zero volts", so don't get it twisted 🙈
• channels — a const struct iio_chan_spec * pointing at the channel specification. It's giving main character pointer energy 👑
• num_channels — an unsigned int, and it's literally just the number of channels. That's it. That's the field 🍓
• regmap_type — an enum ad5064_regmap_type, which is the register map layout variant. Different chips, different layouts, iykyk 🌸

🌈 SEE ALSO 🌈

• Kernel file ./drivers/iio/dac/ad5064.c
• enum ad5064_regmap_type(9)
• struct ad5064_state(9)

ok bestie real talk: this page lives in ./drivers/iio/dac and it's dated October 2026, and the whole thing is filed under struct ad5064_chip_info(9) in the Kernel API Manual. Go read the source, it ate 💀🔥

That's the whole page, periodt. Now go forth and read your chip info sheets 💜🧚‍♀️