STRUCT OMAP_OPP_DEF(9)

🌸 NAME 🌸

struct omap_opp_def — OMAP OPP Definition, and bestie this is literally the Kernel API Manual page for it 💖

✨ SYNOPSIS ✨

okay so the struct is giving very “here is the whole vibe” energy, no cap:

       struct omap_opp_def {
           char *hwmod_name;
           unsigned long freq;
           unsigned long u_volt;
           bool default_available;
        };

🫶 Members 🫶

• hwmod_name — the name of the hwmod for this domain 🛠️
• freq — frequency in hertz corresponding to this OPP ⚡
• u_volt — nominal voltage in microvolts corresponding to this OPP 🔋
• default_available — True/false — is this OPP available by default? 🎀

🎀 Description 🎀

okay so picture this: OMAP SOCs have a standard set of tuples consisting of frequency and voltage pairs that the device will support per voltage domain. this is called Operating Points or OPP, periodt ✨

ngl the actual definitions of OMAP Operating Points varies over silicon within the same family of devices — yes, even within the same fam, it’s giving variety 😭. for a specific domain, you can have a set of {frequency, voltage} pairs and this is denoted by an array of omap_opp_def. as the kernel boots and more information is available, a set of these are activated based on the precise nature of device the kernel boots up on. main character energy fr fr 👑

and the way that it is interesting to remember: each IP which belongs to a voltage domain may define their own set of OPPs on top of this — but this is handled by the appropriate driver. iykyk 💅

🔥 SEE ALSO 🔥

• Kernel file ./arch/arm/mach-omap2/omap_opp_data.h 📁

xoxo bestie 💜 — this page comes from ./arch/arm/mach-omap2, dated October 2026, and it’s literally the struct omap_opp_def(9) page. slay ✨