STRUCT VID_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ struct vid_data(9) β€” the voltage data glow-up

okay bestie, so the page header says struct vid_data(9) and the manual name is Kernel API Manual β€” yes, the kernel API manual, we're in the big leagues now ✨


🌸 NAME 🌸

struct vid_data β€” literally stores voltage information data, that's the whole vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct vid_data {
    int min;
    int max;
    int turbo;
    int32_t ratio;
 };

no cap, that's the whole struct β€” four juicy little fields, icon energy πŸ‘‘


✨ Members ✨

  • min β€” the VID data for this platform that corresponds to the lowest P state πŸ“
  • max β€” the VID data that corresponds to the highest P State πŸ’…
  • turbo β€” the VID data for the turbo P state πŸ”₯
  • ratio β€” the ratio of (vid max - vid min) / (max P state - Min P State), math queen behavior 🧚

πŸ’– Description πŸ’–

so what is this even for? struct vid_data stores the voltage data for DVFS (Dynamic Voltage and Frequency Scaling) β€” yes, say it with your chest, DVFS πŸ’€

this data gets used in Atom platforms, where β€” on top of the target P state β€” the voltage data also needs to be specified so the next P State can be selected. it's giving "extra step but make it necessary" πŸ™ˆ

fr fr, that's not me adding lore, that's just what the page says β€” the voltage data is a required part of picking the next P State on those platforms 🫢

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/cpufreq/intel_pstate.c β€” go read the source, iykyk πŸ‘€
  • struct sample(9)
  • struct pstate_data(9)
  • struct global_params(9)
  • struct cpudata(9)
  • struct pstate_funcs(9)

like, the whole intel_pstate.c friend group, honestly πŸ’œ


and that's the page, bestie β€” slay, you now understand struct vid_data πŸ’…

this one lives under ./drivers/cpufreq and the page is dated October 2026, so like… bookmark it, timestamp it, screenshot it, whatever you gotta do β­πŸŽ€

πŸ“¦ where this page comes from