dev_pm_opp_of_register_em(9)

📦 version 7.3.1, in nixpkgs unstable

✨ dev_pm_opp_of_register_em ✨

okay so bestie, welcome to the Kernel API Manual 💖 this one's a little function from the kernel, and honestly? it's giving "small but mighty." let's get into it 🫶

🌸 NAME 🌸

dev_pm_opp_of_register_em — the "hey, let's try to register an Energy Model" girlie 💅

🦋 SYNOPSIS 🦋

int dev_pm_opp_of_register_em (struct device *dev , struct cpumask *cpus );

like, it returns an int, it takes a struct device *dev and a struct cpumask *cpus, and that's the whole vibe ✨

🎀 ARGUMENTS 🎀

  • dev — the device we wanna register an Energy Model for 👑 this is the main character of the call ngl
  • cpus — the CPUs we're registering an Energy Model for 💖 but heads up: for any other type of device, this one should be set to NULL — no cap, just NULL 🙈

🍓 DESCRIPTION 🍓

so what does it actually do? it checks whether the "dynamic-power-coefficient" devicetree property has been specified 👀 and if it has, it tries to register an Energy Model with it. that's it, that's the job 💅

and why do we care? because having this property means the voltages are known for OPPs, and the EM might be calculated 🔥 iykyk — no property, no voltages known, no EM math happening. periodt.

🌈 SEE ALSO 🌈

bestie, the guest list is LONG and everyone's invited 💀 all of these are worth a peek:

like, that's a whole friend group right there 🧚💜

reminder bestie: this is straight from the ./drivers/opp crew, October 2026 edition of the Kernel API Manual — go read the source if you want the deep lore, ok? 💖✨ slay and stay curious 🦋
📦 where this page comes from