omap4_dpll_regm4xen_recalc(9)
π omap4_dpll_regm4xen_recalc π
okay so bestie, welcome to the Kernel API Manual page for omap4_dpll_regm4xen_recalc(9) β yes that name is a whole mouthful, no I will not be shortening it, it's iconic and we respect it π«Ά
β¨ NAME β¨
omap4_dpll_regm4xen_recalc β compute DPLL rate, considering REGM4XEN bit πΈ
π¦ SYNOPSIS π¦
unsigned long omap4_dpll_regm4xen_recalc (struct clk_hw *hw , unsigned
long parent_rate );
like, that's the whole vibe. one function, two args, zero drama π
π ARGUMENTS π
hwβ pointer to the clock you're computing the rate for. it's giving "main character pointer" energy β¨parent_rateβ the clock rate of the DPLL parent. your origin story, basically π
π DESCRIPTION π
so here's the tea β β this function computes the output rate for the OMAP4 DPLL that clk represents. and the way that it does this is it takes the REGM4XEN bit into consideration, which is lowkey essential because the OMAP4 ABE DPLL literally needs it. iykyk π₯
on success it returns the DPLL's output rate (before M-dividers, bestie β before them, don't forget), and on error it returns 0. that's it, that's the whole function, and honestly? she ate πβ¨
ngl, if you get a 0 back, that's the error signal β don't go treating it as a real rate, that's not the move π
π SEE ALSO π
- Kernel file
./drivers/clk/ti/dpll44xx.c omap4_dpll_lpmode_recalc(9)omap4_dpll_regm4xen_determine_rate(9)
go read those too, they're the supporting cast and they understood the assignment π
and that's a wrap, bestie π§ this lil page came from ./drivers/clk/ti, dated October 2026, and it's literally the omap4_dpll_regm4xen_recalc(9) manual β slay, periodt, go compute some rates π
π
π¦ 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