diff options
author | Marc Zyngier <Marc.Zyngier@arm.com> | 2015-09-28 15:49:12 +0100 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-10-01 02:18:38 +0200 |
commit | e647b532275bb357e87272e052fccf5fcdb36a17 (patch) | |
tree | ffb3a3d9e302e5e76cc2466f75c67d097fdbe504 /drivers/s390/char/vmcp.h | |
parent | 233782495f161341a82aa933b42b35c94077bd65 (diff) | |
download | blackbird-op-linux-e647b532275bb357e87272e052fccf5fcdb36a17.tar.gz blackbird-op-linux-e647b532275bb357e87272e052fccf5fcdb36a17.zip |
ACPI: Add early device probing infrastructure
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.
In order to allow some basic probing based on the ACPI tables,
introduce "struct acpi_probe_entry" which contains just enough
data and callbacks to match a table, an optional subtable, and
call a probe function. A driver can, at build time, register itself
and expect being called if the right entry exists in the ACPI
table.
A acpi_probe_device_table() is provided, taking an identifier for
a set of acpi_prove_entries, and iterating over the registered
entries.
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Reviewed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Reviewed-by: Hanjun Guo <hanjun.guo@linaro.org>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Hanjun Guo <hanjun.guo@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/s390/char/vmcp.h')
0 files changed, 0 insertions, 0 deletions