_omap3_noncore_dpll_lock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

_omap3_noncore_dpll_lock β€” instruct a DPLL to lock and wait for readiness πŸ’–

Okay bestie, welcome to the Kernel API Manual page for _omap3_noncore_dpll_lock β€” yes, we're literally doing this, and yes, it's giving clock-framework main character energy πŸ‘‘.

✨ SYNOPSIS ✨

int _omap3_noncore_dpll_lock (struct clk_hw_omap *clk );

πŸŽ€ ARGUMENTS πŸŽ€

  • clk β€” pointer to a DPLL struct clk πŸ’…

πŸ’– DESCRIPTION πŸ’–

Okay so here's the vibe: this one instructs a non-CORE DPLL to lock. It waits for the DPLL to report readiness before returning β€” no rushing the process, bestie 😭.

It will save and restore the DPLL's autoidle state across the enable, per the CDP code. That's the whole little glow-up ✨.

If the DPLL locked successfully, it returns 0; if the DPLL did not lock in the time allotted, or DPLL3 was passed in, it returns -EINVAL β€” periodt πŸ’€.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/clk/ti/dpll3xxx.c β€” and honestly, the whole clique is right here:


okay that's the whole page, bestie 🫢 β€” source/version: ./drivers/clk/ti, date: October 2026, and the page title is literally _omap3_noncore_dpll_lock(9) πŸ’œβœ¨

πŸ“¦ where this page comes from