pse_pw_d_is_sw_pw_control(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pse_pw_d_is_sw_pw_control β€” like, is this power control a software girlie or what?

okay bestie, welcome to pse_pw_d_is_sw_pw_control(9) from the Kernel API Manual ✨ this one's a tiny little yes/no function and honestly it ate πŸ’–


✨ NAME ✨

pse_pw_d_is_sw_pw_control β€” figure out whether the power control is managed by software, no cap 🫢


🌸 SYNOPSIS 🌸

bool pse_pw_d_is_sw_pw_control (struct pse_controller_dev *pcdev ,
struct pse_power_domain *pw_d );

πŸŽ€ ARGUMENTS πŸŽ€

  • pcdev β€” a pointer to the PSE controller device πŸ‘‘ like, the controller itself, bestie
  • pw_d β€” a pointer to the PSE power domain πŸ¦‹ the specific domain we're doing a vibe check on

πŸ’œ DESCRIPTION πŸ’œ

So this function literally just determines whether the power control for a specific power domain is managed by software in the interrupt handler, rather than directly by hardware πŸ’… yes, that distinction matters, iykyk.

Software power control is active in these cases, periodt:

  • When the budget evaluation strategy is set to static ⭐
  • When the budget evaluation strategy is disabled but the PSE controller has an interrupt handler that can report if a Powered Device is connected πŸ”₯

🌈 RETURN 🌈

  • true if the power control of the power domain is managed by software 🧚✨
  • false otherwise πŸ’€ (no software control energy today, sorry)

πŸ“ SEE ALSO πŸ“

Kernel file ./drivers/net/pse-pd/pse_core.c, plus the whole friend group:


mwah πŸ’‹ that's the whole page! This lil cutie lives in ./drivers/net/pse-pd, and this version is the October 2026 era πŸ—“οΈβœ¨ slay, go read the source, ily, bye πŸ«ΆπŸ’–

πŸ“¦ where this page comes from