usb_acpi_set_power_state(9)

✨ usb_acpi_set_power_state(9) ✨

okay so this is a page from the Kernel API Manual and honestly? it's a little baddie for controlling your usb port's power. welcome bestie 💖

---

🌸 NAME 🌸

usb_acpi_set_power_state — it literally controls a usb port's power via the acpi power resource. that's the whole vibe. 🎀

---

🦋 SYNOPSIS 🦋

int usb_acpi_set_power_state (struct usb_device *hdev , int index , bool
enable );

yes bestie, she takes three things and she gives you back an int. no cap.

---

💅 ARGUMENTS 💅

• hdev — the USB device that belongs to the usb hub. like, the actual device in question, okay? 🫶
• index — the port index, and it's zero-based (so the first one is 0, not 1, don't come for me, that's just how it is). 🔥
• enable — the power state that's expected to be set. it's a bool, so it's giving yes/no energy. ✨

---

👑 DESCRIPTION 👑

Heads up, bestie, this is important: before you invoke this function, you gotta use usb_acpi_power_manageable to check whether the usb port even has an acpi power resource. like, do the vibe check first. 💀

It returns 0 on success — and otherwise a negative errno. so if you get a negative number back, something did not slay. 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/usb/core/usb-acpi.c 👀
• usb_acpi_power_manageable(9) — the one you check with first, remember? 💜
• usb_acpi_port_lpm_incapable(9)
• usb_acpi_add_usb4_devlink(9)

---

fr fr read the DESCRIPTION again before you call this. the usb_acpi_power_manageable check is not optional, it's main character energy. ⭐

---

okay that's the whole page, bestie!! 🍓 this one lives in ./drivers/usb/core, and it's dated October 2026 — and yeah, she's still usb_acpi_set_power_state(9) through and through. periodt. 🧚💖🎀