dev_pm_opp_adjust_voltage(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dev_pm_opp_adjust_voltage β€” Kernel API Manual

okay so bestie, welcome to the glow-up page for dev_pm_opp_adjust_voltage(9). This is a kernel API manual, and we're about to make voltage tweaks make sense. ✨


🌸 NAME

dev_pm_opp_adjust_voltage β€” the little helper whose whole job is changing the voltage of an OPP. That's it, that's the vibe. πŸŽ€


πŸ¦‹ SYNOPSIS

int dev_pm_opp_adjust_voltage (struct device *dev , unsigned long freq ,
unsigned long u_volt , unsigned long u_volt_min , unsigned long
u_volt_max );

Like, five arguments, one int back. Slay. πŸ’…


πŸ’– ARGUMENTS

  • dev β€” the device we're doing this whole operation for. Main character energy, honestly.
  • freq β€” the OPP frequency whose voltage you wanna adjust. Find it first, okay?
  • u_volt β€” the new OPP target voltage. The moment. The goal. πŸ‘‘
  • u_volt_min β€” the new OPP min voltage, because boundaries are healthy.
  • u_volt_max β€” the new OPP max voltage. Ceiling queen. 🌈

⭐ RETURN

  • -EINVAL β€” bad pointers, bestie. Like, the pointer vibe check failed. 😭
  • -ENOMEM β€” no memory available for the copy operation. Not enough room, it's giving crowded.
  • 0 β€” returns 0 if no modification was done OR if the modification was successful. Yes, both. Iconic, confusing, periodt. πŸ’€
ngl, that last one is a real "was anything even done?" moment, but that's literally what it says, so. 🫢

🧚 SEE ALSO

The kernel file ./drivers/opp/core.c and, like, the entire OPP friend group β€” no cap, here's everyone:


and that's the whole page, bestie πŸ’œ

shoutout to the source at ./drivers/opp and the date October 2026 β€” this one's brought to you by the dev_pm_opp_adjust_voltage(9) girlies, published in the Kernel API Manual. go adjust some voltage, ily πŸŽ€πŸ’–

πŸ“¦ where this page comes from