From: Marc Zyngier <marc.zyngier@arm.com>
To: Hanjun Guo <hanjun.guo@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Tomasz Nowicki <tn@semihalf.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: linaro-acpi@lists.linaro.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] ACPI probing infrastructure
Date: Fri, 11 Sep 2015 15:06:47 +0100 [thread overview]
Message-ID: <55F2DFF7.6090301@arm.com> (raw)
In-Reply-To: <55F14753.5070703@linaro.org>
On 10/09/15 10:03, Hanjun Guo wrote:
> On 09/08/2015 09:19 PM, Hanjun Guo wrote:
>> Hi Marc,
>>
>> Sorry for the late response for quite a while...
>>
>> On 09/05/2015 01:06 AM, 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.
>>>
>>> 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 :)
>
>>
>> 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 <hanjun.guo@linaro.org>
> Reviewed-by: Hanjun Guo <hanjun.guo@linaro.org>
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...
prev parent reply other threads:[~2015-09-11 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 17:06 [PATCH 0/5] ACPI probing infrastructure Marc Zyngier
2015-09-04 17:06 ` [PATCH 1/5] acpi: Add basic device " Marc Zyngier
2015-09-07 16:00 ` Lorenzo Pieralisi
2015-09-07 17:35 ` Marc Zyngier
2015-09-07 21:29 ` Rafael J. Wysocki
2015-09-08 9:57 ` Marc Zyngier
2015-09-08 13:01 ` Hanjun Guo
2015-09-04 17:06 ` [PATCH 2/5] irqchip/acpi: Add probing infrastructure for ACPI-based irqchips Marc Zyngier
2015-09-04 17:06 ` [PATCH 3/5] irqchip/gic: Convert the GIC driver to ACPI probing Marc Zyngier
2015-09-04 17:06 ` [PATCH 4/5] clocksource/acpi: Add probing infrastructure for ACPI-based clocksources Marc Zyngier
2015-09-04 17:06 ` [PATCH 5/5] clocksource/arm_arch_timer: Convert to ACPI probing Marc Zyngier
2015-09-07 6:58 ` [PATCH 0/5] ACPI probing infrastructure Tomasz Nowicki
2015-09-08 14:38 ` Tomasz Nowicki
2015-09-07 21:26 ` Rafael J. Wysocki
2015-09-08 9:45 ` Marc Zyngier
2015-09-08 22:26 ` Rafael J. Wysocki
2015-09-08 13:19 ` Hanjun Guo
2015-09-10 9:03 ` Hanjun Guo
2015-09-11 14:06 ` Marc Zyngier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55F2DFF7.6090301@arm.com \
--to=marc.zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=hanjun.guo@linaro.org \
--cc=jason@lakedaemon.net \
--cc=lenb@kernel.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=tn@semihalf.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).