Thread (19 messages) 19 messages, 5 authors, 2015-09-11

[PATCH 0/5] ACPI probing infrastructure

From: Marc Zyngier <hidden>
Date: 2015-09-11 14:06:52
Also in: linux-acpi, lkml

On 10/09/15 10:03, Hanjun Guo wrote:
On 09/08/2015 09:19 PM, Hanjun Guo wrote:
quoted
Hi Marc,

Sorry for the late response for quite a while...

On 09/05/2015 01:06 AM, Marc Zyngier wrote:
quoted
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.

I'm sure there is some more code to be deleted, and one can only
wonder why this wasn't done before the arm64 code was initially merged
(the diffstat says it all...).

Patches are against v4.2, and a branch is available at

git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
acpi/device-probing
I pulled, and noticed that there is v2, it's cleaner than v1 for the
patch 1/5 to me :)
quoted
Great thanks to cleanup these stuff, I will test
this patch set and review it, will get back to you
if I get anything.
I tested the v2 and it boots pretty happy as before, if
you post to maillist,

Tested-by: Hanjun Guo <redacted>
Reviewed-by: Hanjun Guo <redacted>
I'm still working on v2, so I'm afraid this is still a bit premature.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help