omap2_clk_dflt_find_idlest(9)

🦋 omap2_clk_dflt_find_idlest(9) 🦋

okay so bestie, we're in the Kernel API Manual and this page is literally all about omap2_clk_dflt_find_idlest(9) — the default little helper that goes looking for IDLEST info. no cap, it's a niche one, but we ate. 💅

---

🌸 NAME 🌸

omap2_clk_dflt_find_idlest — find CM_IDLEST reg va, bit shift for @clk ✨

✨ SYNOPSIS ✨

void omap2_clk_dflt_find_idlest (struct clk_hw_omap *clk , struct
       clk_omap_reg *idlest_reg , u8 *idlest_bit , u8 *idlest_val );

🎀 ARGUMENTS 🎀

• clk — struct clk * to find IDLEST info for. the main character we're investigating 🕵️‍♀️
• idlest_reg — void __iomem ** to return the CM_IDLEST va in. yes, the va goes right here 💖
• idlest_bit — u8 * to return the CM_IDLEST bit shift in. the bit-shift drop spot ✨
• idlest_val — u8 * to return the idle status indicator. the vibe check result lands here 🌈

💫 DESCRIPTION 💫

so this function returns the CM_IDLEST register address and bit shift for the module that "owns" this clock. that's the whole mission, and it's giving "default path, but make it useful" 🫶

the default code assumes two things, bestie:

• the CM_IDLEST bit shift is the CM_*CLKEN bit shift 🔥
• the IDLEST register address ID corresponds to the CM_*CLKEN register address ID — for example, that CM_FCLKEN2 corresponds to CM_IDLEST2 💅

heads up: this is not true for all modules. the defaults are defaults, not universal truths, okay? 🙈

and no return value. it's a void function, so it literally returns nothing — periodt. 💀

🔥 SEE ALSO 🔥

Kernel file ./drivers/clk/ti/clkt_dflt.c: _wait_idlest_generic(9), _omap2_module_wait_ready(9), omap2_clk_dflt_find_companion(9), omap2_dflt_clk_enable(9), omap2_dflt_clk_disable(9), omap2_dflt_clk_is_enabled(9) 👑

---

okay byeee, cute sign-off time: source/version is ./drivers/clk/ti, date is October 2026, and the page is omap2_clk_dflt_find_idlest(9) — love that for us 💖🦋🎀