STRUCT OMAP_VP_INSTANCE(9)
πΈ struct omap_vp_instance(9) πΈ
okay so bestie, this is a page from the Kernel API Manual about struct omap_vp_instance β the VP register offsets, per-VDD π
keep that in your pocket, we're going in.
β¨ NAME β¨
struct omap_vp_instance β VP register offsets (per-VDD)
π¦ SYNOPSIS π¦
struct omap_vp_instance {
const struct omap_vp_common *common;
u8 vpconfig;
u8 vstepmin;
u8 vstepmax;
u8 vlimitto;
u8 vstatus;
u8 voltage;
u8 id;
bool enabled;
};
like, that's the whole shape of it, no cap π«Ά
π Members π
commonβ pointer tostruct omap_vp_common *for this SoCvpconfigβPRM_VP*_CONFIGreg offset from PRM startvstepminβPRM_VP*_VSTEPMINreg offset from PRM startvlimittoβPRM_VP*_VLIMITTOreg offset from PRM startvstatusβPRM_VP*_VSTATUSreg offset from PRM startvoltageβPRM_VP*_VOLTAGEreg offset from PRM startidβ Unique identifier for VP instance.enabledβ flag to keep track of whether vp is enabled or not
π real talk: vstepmax is literally sitting there in the struct in the SYNOPSIS and it does not get its own little bullet down here. that's just how the page is, bestie, i don't make the rules, i just relay them faithfully β¨
π Description π
XXX vp_common is probably not needed since it is per-SoC
(it's giving "left a note for future me" energy ngl π)
π§ SEE ALSO π§
Kernel file ./arch/arm/mach-omap2/vp.h struct omap_vp_ops(9), struct omap_vp_common(9)
and that's the whole vibe check, bestie π this one lives at ./arch/arm/mach-omap2, dated October 2026, and the page itself is struct omap_vp_instance(9) β go off, you understood it, i'm so proud of you fr fr πβ¨π
π¦ 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