STRUCT MCP4725_PLATFORM_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 struct mcp4725_platform_data(9) 🌸

okay bestie, welcome to the Kernel API Manual β€” yes we're in that part of the kernel, the part where a DAC gets its own little struct and honestly? iconic. this page is about struct mcp4725_platform_data, no cap πŸ’…


✨ NAME ✨

struct mcp4725_platform_data β€” MCP4725/6 DAC specific data πŸŽ€ like, the little bundle of settings that tells the driver how you want your DAC to behave. she's small. she's specific. she slays.


πŸ¦‹ SYNOPSIS πŸ¦‹

struct mcp4725_platform_data {
    bool use_vref;
    bool vref_buffered;
 };

two bools. that's the whole struct. lowkey elegant, highkey minimal 🫢


πŸ’– Members πŸ’–

  • use_vref β€” whether an external reference voltage on the Vref pin should be used. and heads up: when you turn this on, an additional vref-supply must be specified. no supply, no vibe. 🧚
  • vref_buffered β€” controls buffering of the external reference voltage. that's it, that's the whole job. she buffers. 🌈

πŸŽ€ Description πŸŽ€

okay so here's the tea β˜• β€” the Vref related settings are available only on MCP4756 πŸ‘‘ so don't come for the other chips expecting vref magic, they simply don't have it.

want the full lore? go read Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml for more information. it's giving "the source of truth" fr fr πŸ“œβœ¨


⭐ SEE ALSO ⭐

  • Kernel file ./include/linux/iio/dac/mcp4725.h β€” go peek, iykyk πŸ’œ

bestie reminder 🌸: use_vref without a vref-supply is a whole mess β€” the docs say it must be specified when used, so pls don't skip it πŸ™ˆ

that's the page!! short, sweet, and fully documented β€” this one came from ./include/linux/iio/dac, dated October 2026, and it's out here doing main character energy in struct mcp47...latform_data(9). periodt πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from