acpi_subsystem_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… acpi_subsystem_init β€” a kernel API manual moment

Okay bestie, gather round, because we're looking at acpi_subsystem_init(9) from the Kernel API Manual and honestly? It's a little one, but it's a load-bearing little one. Let's get into it 🫢


✨ NAME ✨

acpi_subsystem_init β€” the function that finalizes the early initialization of ACPI. That's it, that's the whole job, and it slays at it πŸ’–


🌸 SYNOPSIS 🌸

void acpi_subsystem_init (void );

Yep. That's the whole signature. No cap.


πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments. Nothing. Zero. She takes nothing and she gives everything πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

So what does she actually do? She switches the platform over to ACPI mode β€” if possible. That "if possible" is doing a lot of work, so keep it in your back pocket πŸ™ˆ

Now here's the vibe check that matters: doing this too early is generally unsafe. Like, genuinely, not in a cute way. But at the same time β€” and this is the plot twist β€” it needs to be done before all the things that really depend on ACPI. So you're threading a needle here πŸͺ‘

The right spot appears to be before finalizing the EFI initialization. That's the sweet spot, the main character placement, the moment where everything lines up ✨

Not me stressing the timing on this one β€” early = unsafe, late = everything downstream that depends on ACPI is grumpy. Before finalizing EFI init. That's the assignment πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/acpi/bus.c and the whole friend group:


🌈 sign-off 🌈

That's the whole page, bestie β€” brought to you from ./drivers/acpi, dated October 2026, in the Kernel API Manual πŸ’œ Go forth and initialize your ACPI subsystem at exactly the right moment, not a second earlier. Periodt 🧚⭐

πŸ“¦ where this page comes from