Re: [PATCH 0/5] ACPI probing infrastructure

From: Rafael J. Wysocki
Date: Mon Sep 07 2015 - 16:58:50 EST

On Friday, September 04, 2015 06:06:47 PM Marc Zyngier wrote:
> IRQ controllers and timers are the two types of device the kernel
> requires before being able to use the device driver model.
> ACPI so far lacks a proper probing infrastructure similar to the one
> we have with DT, where we're able to declare IRQ chips and
> clocksources inside the driver code, and let the core code pick it up
> and call us back on a match. This leads to all kind of really ugly
> hacks all over the arm64 code and even in the ACPI layer.
> It turns out that providing such a probing infrastructure is rather
> easy, and provides a much deserved cleanup in both the arch code, the
> GIC driver, and the architected timer driver.

Since I'm not familiar with the DT probing infrastructure mentioned above,
can you please explain to me (possibly at a high level), how it is supposed
to work in the ACPI case?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at