psp_check_pl...ccess_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… psp_check_pl...ccess_status(9)

okay bestie, so this is psp_check_platform_access_status β€” a kernel API manual page from the Kernel API Manual, and yeah the title is truncated like that in the header because life is short and man page headers are shorter 🫢


✨ NAME ✨

psp_check_platform_access_status β€” literally just checks whether the platform features are ready. that's the whole gig. no cap πŸ’…


🌸 SYNOPSIS 🌸

int psp_check_platform_access_status (void );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • void β€” no arguments, bestie. nothing. zero. the function said "i need nobody" and honestly? iconic.

πŸ’– DESCRIPTION πŸ’–

okay so here's the vibe: this function is intended to be used by drivers outside of ccp to figure out whether platform features have initialized yet.

that's it. that's the function. it's giving "are we there yet" but for platform features. main character energy for real 🌈


⭐ RETURN ⭐

  • 0 β€” platform features is ready βœ… slay, we're good
  • -ENODEV β€” platform features is not ready or present 😭 no device vibes, come back later (or never)
fr fr, don't sleep on that second one β€” if you get -ENODEV back, the features aren't ready or they're straight up not there. two moods, same errno πŸ’€

πŸ”₯ SEE ALSO πŸ”₯


and that's the whole page, bestie ✨ this one lives in ./include/linux and the date on it is October 2026, so like… future vibes only πŸ§šπŸ’œ mwah, go check those platform features πŸ’…πŸŽ€

πŸ“¦ where this page comes from