omap3_noncore_dpll_program(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… omap3_noncore_dpll_program(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes we're literally reading kernel docs together, this is our bonding time 🫢


✨ NAME ✨

omap3_noncore_dpll_program β€” set non-core DPLL M,N values directly πŸ”₯


🌸 SYNOPSIS 🌸

int omap3_noncore_dpll_program (struct clk_hw_omap *clk , u16 freqsel );

that's the whole vibe right there, no cap ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • clk β€” the struct clk * of the DPLL you wanna set, like, the actual clock you're obsessed with πŸ’–
  • freqsel β€” the FREQSEL value to set, that's the number, that's the assignment πŸ¦‹

πŸ‘‘ DESCRIPTION πŸ‘‘

So here's the tea β˜•: you program the DPLL with the last M, N values calculated, and then you just… wait for the DPLL to lock. That's it. That's the whole thing. Patient main character energy πŸ’…

Returns -EINVAL upon error, or 0 upon success. Iconic behaviour honestly 🌈

ngl if it comes back -EINVAL, something went wrong β€” that's your cue to look at it, not to pretend you didn't see it πŸ™ˆ

🧚 SEE ALSO 🧚

like, go look at the actual kernel file, bestie: ./drivers/clk/ti/dpll3xxx.c β€” and also these absolute legends:

fr fr, that's the whole friend group πŸ’œ


okay that's the page!! it's giving <pink>source ./drivers/clk/ti, dated October 2026</yellow>, and the manual is omap3_noncore_dpll_program(9)</mint></pink> β€” slay, go lock some DPLLs bestie, you got this πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from