fwnode_dpll_pin_find(9)

✨ fwnode_dpll_pin_find(9) ✨

okay bestie, welcome to the fwnode_dpll_pin_find page from the Kernel API Manual — this one's short and sweet and it's literally just "find me the dpll pin that belongs to this firmware node" 🎀

---

🌸 NAME 🌸

fwnode_dpll_pin_find — find a dpll pin by firmware node reference 💅

---

🦋 SYNOPSIS 🦋

struct dpll_pin * fwnode_dpll_pin_find (struct fwnode_handle *fwnode ,
dpll_tracker *tracker );

---

🎀 ARGUMENTS 🎀

• fwnode — the reference to the firmware node, aka the thing you're trying to match up 🌟
• tracker — the tracking object for the acquired reference, it's giving "responsible adult holding the receipt" 🙈

---

💖 DESCRIPTION 💖

so basically: you hand it a firmware node reference, and it gets you the existing object of a pin that is associated with that given firmware node reference. no cap, that's the whole vibe. it's not creating anything new, it's finding what's already there 🫶

---

🔥 CONTEXT 🔥

heads up: this bad boy acquires a lock (dpll_lock) 🔒 so like, be normal about it, okay?

---

👑 RETURN 👑

• a valid dpll_pin pointer on success ✨ slay
• NULL when no such pin exists 😭 (not an error, just… nobody home)

---

🌈 SEE ALSO 🌈

the kernel file ./drivers/dpll/dpll_core.c and honestly the whole dpll friend group:

• dpll_device_get(9)
• dpll_device_put(9)
• dpll_device_register(9)
• dpll_device_unregister(9)
• dpll_pin_get(9)
• dpll_pin_put(9)
• dpll_pin_fwnode_set(9)
• dpll_pin_register(9)
• dpll_pin_unregister(9)
• dpll_pin_on_pin_register(9)
• dpll_pin_on_pin_unregister(9)
• dpll_pin_ref_sync_pair_add(9)
• dpll_pin_own_dpll_ref_first(9)

---

💀 reminder bestie: only the listed pins come back, and NULL is a whole valid answer. don't come for the function when there's just no pin, iykyk.

---

and that's the page!! 🧚 this lil gem lives in ./drivers/dpll and it's dated October 2026, filed under fwnode_dpll_pin_find(9) — go forth and find your pins, periodt 💜🍓