dpll_pin_own_dpll_ref_first(9)
π dpll_pin_own_dpll_ref_first(9) π
okay so bestie, welcome to the Kernel API Manual β yes we're reading kernel docs together, that's just the kind of friendship we have π«Ά
β¨ NAME β¨
dpll_pin_own_dpll_ref_first β find the first owner dpll ref of a pin π
β¨ SYNOPSIS β¨
struct dpll_pin_ref * dpll_pin_own_dpll_ref_first (struct dpll_pin *pin
);
β¨ ARGUMENTS β¨
pinβ pointer to a dpll pin πΈ (that's the little guy we're investigating)
β¨ DESCRIPTION β¨
okay so here's the vibe π« β this function goes digging through pin's dpll_refs, searching for a ref whose dpll matches the pin's (module, clock_id) tuple. iykyk, that means: the dpll that was registered by the driver that created the pin β its actual owner π.
why do we care bestie? because this makes sure pin-level attributes get reported and modified using the owner's ops π€ even when that same pin is also registered with dplls from other drivers. like yes the pin is popular and hangs out with lots of dplls, but the owner still gets the final say. main character energy fr fr π
β¨ RETURN β¨
pointer to the owner's dpll_pin_ref π― β or NULL if no owner ref is found π (no owner, no ref, sad times)
β¨ SEE ALSO β¨
Kernel file ./drivers/dpll/dpll_core.c π plus all these iconic functions:
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)fwnode_dpll_pin_find(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)
okay that's the whole page, you ate that π go forth and find those owner refs bestie!! π
anyway this lil masterpiece lives in ./drivers/dpll, dated October 2026, and it's filed under dpll_pin_own_dpll_ref_first(9) β periodt πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms