pwrseq_enable(9)

✨ pwrseq_enable(9) ✨

okay so bestie, welcome to pwrseq_enable(9) from the Kernel API Manual — this is the lil kernel function that slides into the power sequencer's DMs and is like "hey queen, the consumer device would like to be ON please 💅"

---

🌸 NAME 🌸

pwrseq_enable — issue a power-on request on behalf of the consumer device 💖

---

🎀 SYNOPSIS 🎀

int pwrseq_enable (struct pwrseq_desc *desc );

like literally that's the whole vibe check, no cap 🫶

---

🦋 ARGUMENTS 🦋

• desc — the descriptor that references the power sequencer. it's giving "here's my ID, let me in" energy 👑

---

⭐ DESCRIPTION ⭐

so this function tells the power sequencer that the consumer wants to be powered-up. main character request, honestly 🔥

here's the tea though, there are three situations and you gotta know which one you're in:

• the sequencer may already have powered-up the device — in which case the function just returns 0 and you can go about your day 🌈
• if the power-up sequence is already in progress, the function will block until it's done, then return 0. yes bestie, it waits. patient icon behavior 🧚
• if this is the first request, the device will be powered up. periodt 💅

---

👑 RETURN 👑

• 0 on success 💚
• negative error number on failure 💀

---

💜 SEE ALSO 💜

okay this list is long but every single one matters, don't skip, iykyk:

• Kernel file ./drivers/power/sequencing/core.c
• struct pwrseq_unit(9)
• struct pwrseq_unit_dep(9)
• struct pwrseq_target(9)
• struct pwrseq_device(9)
• struct pwrseq_desc(9)
• pwrseq_device_register(9)
• pwrseq_device_unregister(9)
• devm_pwrseq_device_register(9)
• pwrseq_device_get_drvdata(9)
• pwrseq_get(9)
• pwrseq_put(9)
• devm_pwrseq_get(9)
• pwrseq_disable(9)
• pwrseq_to_device(9)

---

🍓 tiny reminder babe: this page lives at ./drivers/power/sequencing — that's where the sauce is.

---

and that's the whole page, you ate that 💖 this lil masterpiece comes courtesy of ./drivers/power/sequencing, dated October 2026 — stan the power sequencing crew, they're iconic 👑✨🎀