_set_module_autoidle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… _set_module_autoidle β€” like, the Kernel API Manual page, bestie ✨

okay so you found the _set_module_autoidle(9) page in the Kernel API Manual and you're staring at it like πŸ‘οΈπŸ‘„πŸ‘οΈ β€” don't worry, I got you. Sit down, hydrate, let's go 🫢


🌸 NAME 🌸

_set_module_autoidle β€” sets the OCP_SYSCONFIG AUTOIDLE field in v πŸ’«


✨ SYNOPSIS ✨

int _set_module_autoidle (struct omap_hwmod *oh , u8 autoidle , u32 *v );

like yes that's the whole signature, she's short and she knows it πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • oh β€” a struct omap_hwmod *. the hwmod in question, the main character of this whole situation πŸ‘‘
  • autoidle β€” the AUTOIDLE bitfield value you want, and it's literally just 0 or 1. that's it. binary queen πŸ¦‹
  • v β€” pointer to the register contents you're about to mess with ✍️

πŸ’– DESCRIPTION πŸ’–

so what this does: it updates the module autoidle bit inside v so it matches autoidle, for the hwmod you passed in as oh. simple, clean, no drama ✨

and the autoidle bit? it controls whether the module can gate its internal clocks automatically when it isn't doing anything β€” like the module is just vibing, not working, so it dims the lights on itself πŸ’€ but ngl, the exact function of this bit varies on a per-module basis, so don't come for me with "but on module X it does Y" β€” iykyk πŸ™ˆ

🚨 important one bestie: this function does NOT write to the hardware. no cap. it just edits the value in your register contents and leaves the actual hardware alone. so don't expect the silicon to change, because she will not πŸ’€

it returns -EINVAL on error, or 0 on success. slay βœ…


πŸ¦‹ SEE ALSO πŸ¦‹

like, that's the whole friend group, she's very well connected 🫢


🌈 ok that's the whole page bestie, go forth and autoidle responsibly πŸ’œ β€” this one lives in ./arch/arm/mach-omap2 and the version vibes are from October 2026. mwah, bye πŸ’…πŸŽ€

πŸ“¦ where this page comes from