dpll_pin_ref_sync_pair_add(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dpll_pin_ref_sync_pair_add(9) β€” the kernel API manual, but make it make sense

okay so bestie, this is a page from the Kernel API Manual (section 9, kernel land, we love her) and it's all about dpll_pin_ref_sync_pair_add ✨ β€” the function that literally creates a reference sync signal pin pair. That's the whole vibe. Let's get into it 🫢


✨ NAME ✨

dpll_pin_ref_sync_pair_add β€” create a reference sync signal pin pair πŸ’–


🌸 SYNOPSIS 🌸

int dpll_pin_ref_sync_pair_add (struct dpll_pin *pin , struct dpll_pin
       *ref_sync_pin );

πŸŽ€ ARGUMENTS πŸŽ€

  • pin β€” the pin which produces the base frequency. she's the main character of frequencies fr fr πŸ’…
  • ref_sync_pin β€” the pin which produces the sync signal. the supporting icon that keeps everything in sync ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: once pins are paired, the user-space configuration of reference sync pair is possible. that's it, that's the whole plot πŸ‘‘

literally β€” pair them up and user space can configure the reference sync pair. no cap πŸ’œ


πŸ”₯ CONTEXT πŸ”₯

acquires a lock (dpll_lock). yes bestie, she locks. respect the lock πŸ™ˆ


⭐ RETURN ⭐

  • 0 on success πŸŽ‰
  • negative β€” error value πŸ’€

🌈 SEE ALSO 🌈

kernel file ./drivers/dpll/dpll_core.c β€” plus the whole friend group, all of them, no one left out:

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_own_dpll_ref_first(9)


ok that's the whole page bestie, go forth and pair your pins πŸ’–

mwah πŸ’‹ β€” this one's from ./drivers/dpll, dated October 2026, and it's the dpll_pin_ref_sync_pair_add(9) page signing off. slay ✨

πŸ“¦ where this page comes from