dev_pm_opp_get_of_node(9)

💅 dev_pm_opp_get_of_node(9) 💅

Okay so bestie, welcome to the Kernel API Manual ✨ this is the page for dev_pm_opp_get_of_node, and it's a short one but it's important, so buckle up 🎀

---

🌸 NAME 🌸

dev_pm_opp_get_of_node — gets the DT node corresponding to an opp 🦋

---

✨ SYNOPSIS ✨

struct device_node * dev_pm_opp_get_of_node (struct dev_pm_opp *opp );

---

🫶 ARGUMENTS 🫶

• opp — the opp you want the DT node returned for, like literally the whole point of the call 💖

---

👑 RETURN 👑

The DT node corresponding to the opp, else 0 on success. That's what the page says, no cap, we're not editing it 📝

---

💅 DESCRIPTION 💅

So here's the vibe check: the caller needs to put the node with of_node_put after using it. That's the whole description. Short and iconic, we love a low-maintenance function 🌈

Do not forget the of_node_put, bestie — it's giving "one line of docs, one very real responsibility" 😭

---

⭐ SEE ALSO ⭐

Kernel file ./drivers/opp/of.c, plus the whole friend group:

• dev_pm_opp_of_remove_table(9)
• _opp_add_static_v2(9)
• devm_pm_opp_of_add_table(9)
• dev_pm_opp_of_add_table(9)
• dev_pm_opp_of_add_table_indexed(9)
• devm_pm_opp_of_add_table_indexed(9)
• dev_pm_opp_of_cpumask_remove_table(9)
• dev_pm_opp_of_cpumask_add_table(9)
• dev_pm_opp_of_get_sharing_cpus(9)
• of_get_required_opp_performance_state(9)
• dev_pm_opp_of_has_required_opp(9)
• dev_pm_opp_calc_power(9)
• dev_pm_opp_of_register_em(9)

---

That's the whole page, bestie — short, sweet, and it ate 💜 This little gem lives under ./drivers/opp in the Kernel API Manual, dated October 2026, and yes, it's titled dev_pm_opp_get_of_node(9) because we keep it consistent around here ✨ mwah 🫶