db8500_prcmu_set_epod(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Hey bestie πŸ’– you’re reading the db8500_prcmu_set_epod(9) page from the Kernel API Manual β€” and it’s literally all about setting an EPOD state, no cap.

✨ NAME ✨

db8500_prcmu_set_epod β€” set the state of a EPOD (power domain) πŸ’…βœ¨

πŸŽ€ SYNOPSIS πŸŽ€

int db8500_prcmu_set_epod (u16 epod_id , u8 epod_state );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • epod_id β€” The EPOD to set πŸ‘‘ which one we’re talking about, bestie.
  • epod_state β€” The new EPOD state ✨ the fresh state it’s getting.

🌸 DESCRIPTION 🌸

Okay so this function sets the state of a EPOD (power domain). Simple enough, right? 🫢

But bestie, hear me: it may not be called from interrupt context 😭 like, do not do that. That’s the whole vibe check.

🌈 SEE ALSO 🌈

Kernel file ./drivers/mfd/db8500-prcmu.c is the main-character source πŸ’– and the whole friend group is:


mwah πŸ’‹ sign-off tea: this page’s source/version spot is ./drivers/mfd, the date is October 2026, and the page name is db8500_prcmu_set_epod(9). bye bestie, go set those EPOD states responsibly 🫢✨

πŸ“¦ where this page comes from