pwrseq_disable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ pwrseq_disable β€” Kernel API Manual, bestie edition ✨

okay so this is pwrseq_disable(9), a kernel API manual page, and honestly? it's giving "the breakup text of power management" πŸ’… lowkey essential, highkey underrated. let's get into it 🫢


🌸 NAME 🌸

pwrseq_disable β€” Issue a power-off request on behalf of the consumer device.

like, you're the consumer, and you're officially done, so you file the paperwork to shut things down πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int pwrseq_disable (struct pwrseq_desc *desc );

that's it. that's the whole vibe check. one function, one argument, one int coming back at you ✨


πŸ’œ ARGUMENTS πŸ’œ

  • desc β€” Descriptor referencing the power sequencer. yes bestie, this is the descriptor, the one that knows which power sequencer we're talking about, no cap πŸ”₯

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜• β€” this here function undoes the effects of pwrseq_enable. it's the ✨reverse✨ of the enable, the anti-enable, the "we're so back" to the enable's "it's over."

it issues a power-off request on behalf of the consumer, and when the last remaining user does so, the power-down sequence will be started. the way that the last user out just turns off the lights 😭 iconic behavior fr fr.

and listen β€” if a power-down sequence is already in progress when you call this, the function will block until it's complete and then return. so yes, you will simply have to wait. it's giving "held at the door by the bouncer until the party's actually over" πŸ’€ no skipping ahead, bestie.


⭐ RETURN ⭐

  • 0 on success πŸ’–
  • negative error number on failure 😭 (not me getting a negative number back... wounded)

πŸŽ€ SEE ALSO πŸŽ€

the whole friend group, honestly 🫢 go read them all, iykyk 🌈


and that's the page, bestie 🧚 this little number lives in ./drivers/power/sequencing, dated October 2026 β€” go off, power sequencing directory, we love to see it πŸ‘‘πŸ’œπŸ“

πŸ“¦ where this page comes from