prcmu_get_xp...urrent_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

prcmu_get_xp70_current_state β€” bestie, this one just tells you the current XP70 power mode ✨

Okay so real quick, before we dive in β€” hi, welcome to the Kernel API Manual πŸŽ€, you're gonna do great, and this function is genuinely one of the chillest ones in the whole PRCMU crew. No cap.


🌸 SYNOPSIS 🌸

enum ap_pwrst prcmu_get_xp70_current_state (void );

That's it. That's the whole vibe. She takes nothing, she returns an enum ap_pwrst, she minds her business πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • void β€” literally no arguments. Zero. Nada. Nothing to pass in, nothing to mess up πŸ™ˆ She asks for nothing and gives you the tea anyway.

⭐ RETURN ⭐

So she returns the current AP(ARM) power mode, and it's gonna be one of these, iykyk:

  • init
  • apBoot
  • apExecute
  • apDeepSleep
  • apSleep
  • apIdle
  • apReset

That's the whole set β€” like a little mood ring for your ARM core πŸ‘‘ Whichever one comes back, that's where your AP is at right now. Slay.


🧚 SEE ALSO 🧚

The kernel file lives at ./drivers/mfd/db8500-prcmu.c β€” that's home base, go say hi 🫢

And the whole friend group, in the order the manual gives them (yes, all of them, I'm not skipping a single one, bestie, we don't do that here):

πŸ’€ Also quick heads up: the NAME line in the original is literally prcmu_get_xp...urrent_state(9) up top β€” the title got truncated by the man renderer 'cause it's long. That's not a typo on your end, she just doesn't fit. The function's real full name is prcmu_get_xp70_current_state. πŸ’–

✨ and that's the whole page, bestie ✨ This one's from ./drivers/mfd, dated October 2026, and it's filed under prcmu_get_xp...urrent_state(9) β€” go forth and vibe check your power modes πŸŒˆπŸ’œ

πŸ“¦ where this page comes from