STRUCT MCP4725_PLATFORM_DATA(9)
πΈ 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 additionalvref-supplymust 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_vrefwithout avref-supplyis 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms