dev_pm_opp_get_sharing_cpus(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dev_pm_opp_get_sharing_cpus 💅

okay so this is a page from the Kernel API Manual, section 9, and bestie, it's literally the glow-up guide to finding out which CPUs are vibing on the same OPPs as your fave CPU device. no cap, it's giving "who's in my group chat" energy 🫶

✨ NAME ✨

dev_pm_opp_get_sharing_cpus — get the cpumask of all the CPUs that are sharing OPPs with @cpu_dev, periodt 💅

🌸 SYNOPSIS 🌸

int dev_pm_opp_get_sharing_cpus (struct device *cpu_dev , struct cpumask *cpumask );

like, that's the whole call, bestie — two pointers in, one int out 🔥

🎀 ARGUMENTS 🎀

  • cpu_dev — the CPU device we're doing this whole operation for 👑 it's the main character here
  • cpumask — the cpumask that gets updated with the info about which CPUs are sharing, iykyk 🌈

🦋 DESCRIPTION 🦋

so what it does is: it updates that cpumask with the CPUs that share OPPs with cpu_dev. literally just fills it in with the squad 💖

and the returns? ok so listen:

  • it returns -ENODEV if the OPP table isn't already present 😭 like, no table, no info
  • and it returns -EINVAL if the OPP table's status is access-unknown 🙈
no shade, but if you're getting either of those, your OPP table is not passing the vibe check — check that it's actually there and that its status isn't access-unknown before you blame this function 💀

⭐ SEE ALSO ⭐

kernel file ./drivers/opp/cpu.c plus these iconic siblings:

and that's the page, bestie 🧚 sign-off time: this lil masterpiece lives in ./drivers/opp, dated October 2026, and it's officially titled dev_pm_opp_get_sharing_cpus(9). slay 💜✨

📦 where this page comes from