enable_slot(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enable_slot(9) β€” like, the kernel API manual, but make it make sense πŸ’…

okay bestie, sit down, hydrate, and let me tell you about enable_slot β€” she's a function in the kernel API manual and honestly? she's kind of a big deal πŸŽ€


✨ NAME ✨

enable_slot β€” enable, configure a slot 🫢

like yes, both. enabling AND configuring. she's multi-talented, no cap.


✨ SYNOPSIS ✨

void enable_slot (struct acpiphp_slot *slot , bool bridge );

that's it. that's the whole vibe. void return, two args, she does her thing and dips πŸ’…


✨ ARGUMENTS ✨

  • slot β€” the slot you wanna enable πŸ’– this is the actual struct acpiphp_slot * bestie, the one you're doing the enabling to.
  • bridge β€” a bool, and it's true if the enable is for the whole bridge β€” not just a single slot πŸ‘‘ so like, scope check: one slot or the entire bridge? choose wisely.

✨ DESCRIPTION ✨

okay so this is the part where you gotta pay attention, because it's giving "read the docs before you break prod" energy 😭

this function should be called per physical slot β€” not per each slot object in the ACPI namespace. like, physical slot. fr fr. the namespace might have a whole little collection of slot objects and you do NOT call this for every single one of them, you call it for the real, physical slot. that's the whole point. that's the assignment. 🌸

ngl this is the kind of detail that seems small and then absolutely wrecks your day if you get it wrong, so like… respect the physical slot πŸ’€

✨ SEE ALSO ✨

she's not alone in this codebase, bestie β€” here's the whole friend group, plus where she actually lives:

(and yes, disable_slot(9) and enable_slot are literally right there next to each other β€” opposites attract, main character energy both of them 🌈)


aaaand that's the page!! πŸŽ€ she lives at ./drivers/pci/hotplug, the page is dated October 2026, and she answers to enable_slot(9) β€” mwah, go enable some slots responsibly, ily, bye πŸ’œβœ¨

πŸ“¦ where this page comes from