acpi_device...wer_extended(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… acpi_device_fix_up_power_extended

okay so this is a Kernel API Manual page, bestie β€” and the function it's about is genuinely a little glow-up artist for power states. the page header calls it acpi_device...wer_extended(9) because apparently even the manpage title needs a nap, but the actual star of the show is acpi_device_fix_up_power_extended. iykyk. ✨


🌸 NAME

acpi_device_fix_up_power_extended β€” force a device and all its children into D0.

like, no discussion, no negotiating, everyone's awake now. periodt. πŸ”₯


πŸ¦‹ SYNOPSIS

void acpi_device_fix_up_power_extended (struct acpi_device *adev );

note the void β€” it gives nothing back, it just does. main character energy fr fr. πŸ’…


πŸŽ€ ARGUMENTS

  • adev β€” the parent device object whose power state is the one getting fixed up. she's the ringleader; whatever happens to her trickles down to the kids. 🫢

⭐ DESCRIPTION

so the whole vibe here: you call acpi_device_fix_up_power for adev, and then you keep going and call it for all of adev's children too β€” the full family group chat gets the same message. πŸ’–

the one little caveat, and i'm quoting the rules of the house here: it only does this so long as they are reported as present and enabled. not present? not enabled? she's not bothering β€” those devices can stay exactly where they are. πŸ™ˆ


πŸ‘‘ SEE ALSO

okay this is the long one, and i'm not skipping a single name because everybody on this list matters. no cap. πŸ’€

Kernel file ./drivers/acpi/device_pm.c, plus:

that's the whole squad. read them, love them, cite them. 🌈


and that's the page!! ty for coming to my ted talk, mwah πŸŽ€ β€” this one lives in ./drivers/acpi, and the footer is dated October 2026. see u in the next manpage bestie πŸ’œπŸŒΈβœ¨

πŸ“¦ where this page comes from