STRUCT OMAP_VOLT_DATA(9)

💜 NAME 💜

struct omap_volt_data — the Omap voltage-specific data, aka the little bundle of facts that tells the kernel everything it needs to know about one voltage point. It's giving "voltage dossier" and honestly? Iconic.

✨ SYNOPSIS ✨

struct omap_volt_data {
    u32 volt_nominal;
    u32 sr_efuse_offs;
    u8 sr_errminlimit;
    u8 vp_errgain;
 };

Okay bestie, this is the whole struct — four fields, no cap, and every single one of them is doing main character work. Let's break it down 👇

🎀 Members 🎀

• volt_nominal — the possible voltage value, measured in uV. That's microvolts, so like, tiny numbers of volts. This is the actual voltage this entry is about 💅
• sr_efuse_offs — the offset of the efuse register, and yes that's offset from the system control module base address. That's where you read the n-target value for the smartreflex module from. Think of it as the treasure map coordinate for the n-target value 🗺️✨
• sr_errminlimit — the error min limit value for smartreflex. Here's the tea: this value differs at different opp, so it's literally linked with voltage. It's not a one-size-fits-all situation, bestie 🦋
• vp_errgain — the error gain value for the voltage processor. And just like sr_errminlimit, this field also differs according to the voltage/opp. Two fields, both voltage-dependent, both staying booked and busy 💀🔥

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/platform_data/voltage-omap.h — go read it, iykyk 🫶

lowkey a reminder that these fields are opp-dependent and voltage-dependent, so don't be out here assuming one value works everywhere. That's not the vibe check you want to fail 🙈

and that's the whole page, bestie — struct omap_volt_data(9), from the Kernel API Manual, living in ./include/linux/platform_data, dated October 2026. stan a kernel header for clear skin 💖✨🎀