pci_pwrctrl_...r_on_devices(9)

📦 version 7.3.1, in nixpkgs unstable

💖 pci_pwrctrl_power_on_devices(9) — Kernel API Manual 💖

okay so bestie, you found the man page for pci_pwrctrl_...r_on_devices(9) (yes that's the truncated header name, she's just like that 💅) and honestly? it's a little gem. grab a snack, we're powering things on. ✨

🌸 NAME 🌸

pci_pwrctrl_power_on_devices — literally just powers on pwrctrl devices. that's the whole vibe. 🔥

🦋 SYNOPSIS 🦋

int pci_pwrctrl_power_on_devices (struct device *parent );

🎀 DESCRIPTION 🎀

okay so picture this 👑: you hand it a PCI host controller, and it goes recursively strolling through all the pwrctrl devices in the devicetree hierarchy below that controller — like, the whole family tree, no skipping — and powers them on in a depth first manner. ngl that ordering is the main character here. it goes deep before it goes wide, periodt. 🧚

and the way that it's careful 😭 — if anything goes wrong along the way, every device that already got powered on gets powered off again. a full undo. she does not leave you hanging with half-on hardware, that's such a slay. 💖

🍓 ARGUMENTS 🍓

  • parent — the PCI host controller device. that's your starting point, your anchor, your main character device. 🫶

⭐ RETURN ⭐

  • 0 — success, we ate, everything is on. ✨
  • -EPROBE_DEFER — happens if any pwrctrl driver is not bound. just a "not yet bestie, try again later" situation. ⏳
  • an appropriate error code otherwise. 💀

🌈 SEE ALSO 🌈

like, go read the whole friend group honestly, they all hang out in the same file 🦋💜

ok one tiny heads-up bestie 🙈: the pwrctrl devices it powers on are the ones under the controller you pass in — so make sure that parent is actually the host controller you meant, iykyk.

and that's the page!! 🎀 source is ./drivers/pci/pwrctrl and she's dated October 2026, so mark your calendar babe 🗓️💅 — see you in the next man page, mwah! 💖🌸✨

📦 where this page comes from