From: Hanjun Guo <hanjun.guo@linaro.org>
To: Marc Zyngier <marc.zyngier@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jiang Liu <jiang.liu@linux.intel.com>,
Jason Cooper <jason@lakedaemon.net>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Tomasz Nowicki <tomasz.nowicki@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
Graeme Gregory <graeme@xora.org.uk>
Subject: Re: [PATCH v2 0/7] Making the generic ACPI GSI layer irqdomain aware
Date: Fri, 24 Jul 2015 16:27:52 +0800 [thread overview]
Message-ID: <55B1F708.3010804@linaro.org> (raw)
In-Reply-To: <1437656713-9677-1-git-send-email-marc.zyngier@arm.com>
Hi Marc,
On 07/23/2015 09:05 PM, Marc Zyngier wrote:
> The irqdomain code is not entierely really ACPI friendly, as it has
> some built-in knowledge of the device-tree. Nothing too harmful, but
> enough to scare the ARM ACPI developpers which end up with their own
> version of the square wheel.
>
> This small patch series adapt the irqdomain code to remove the hurdles
> that prevent the full blown irqdomain subsystem to be used on ACPI,
> creates an interface between the GSI layer and the irqdomain, and as
> an example, convert the ARM GIC ACPI support to use irqdomains as
> originally intended.
>
> Overall, this gives us a way to use irqdomains on both DT and ACPI
> enabled platforms, having very little changes made to the actual
> drivers (other than the probing infrastructure). Because we keep the
> flow of information between the various layers identical between ACPI
> and DT, we immediately benefit from the existing infrastructure.
>
> I'd really like to hear what people think of that approach, as it
> looks to me a lot simpler than the other approaches currently put on
> the list. The "convert the GSI information to be DT friendly" is
> admitedly not very pretty, but I see it as a stepping stone towards
> unifying the two structures.
>
> This has been test-booted on Juno, is based on my irq/ncpi-msi-v3
> branch, and available at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/gsi-irq-domain-v2
Pulled and rebased my self-probing and GICv3 ACPI support patches on
top of it, tested on FVP and QEMU, booted OK, for this patch set,
Tested-by: Hanjun Guo <hanjun.guo@linaro.org>
I will sync with Suravee to prepare a single patch for
ACPI self-probing, GICv2m and GICv3 support.
Thank you for putting thing together!
Hanjun
WARNING: multiple messages have this Message-ID (diff)
From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] Making the generic ACPI GSI layer irqdomain aware
Date: Fri, 24 Jul 2015 16:27:52 +0800 [thread overview]
Message-ID: <55B1F708.3010804@linaro.org> (raw)
In-Reply-To: <1437656713-9677-1-git-send-email-marc.zyngier@arm.com>
Hi Marc,
On 07/23/2015 09:05 PM, Marc Zyngier wrote:
> The irqdomain code is not entierely really ACPI friendly, as it has
> some built-in knowledge of the device-tree. Nothing too harmful, but
> enough to scare the ARM ACPI developpers which end up with their own
> version of the square wheel.
>
> This small patch series adapt the irqdomain code to remove the hurdles
> that prevent the full blown irqdomain subsystem to be used on ACPI,
> creates an interface between the GSI layer and the irqdomain, and as
> an example, convert the ARM GIC ACPI support to use irqdomains as
> originally intended.
>
> Overall, this gives us a way to use irqdomains on both DT and ACPI
> enabled platforms, having very little changes made to the actual
> drivers (other than the probing infrastructure). Because we keep the
> flow of information between the various layers identical between ACPI
> and DT, we immediately benefit from the existing infrastructure.
>
> I'd really like to hear what people think of that approach, as it
> looks to me a lot simpler than the other approaches currently put on
> the list. The "convert the GSI information to be DT friendly" is
> admitedly not very pretty, but I see it as a stepping stone towards
> unifying the two structures.
>
> This has been test-booted on Juno, is based on my irq/ncpi-msi-v3
> branch, and available at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/gsi-irq-domain-v2
Pulled and rebased my self-probing and GICv3 ACPI support patches on
top of it, tested on FVP and QEMU, booted OK, for this patch set,
Tested-by: Hanjun Guo <hanjun.guo@linaro.org>
I will sync with Suravee to prepare a single patch for
ACPI self-probing, GICv2m and GICv3 support.
Thank you for putting thing together!
Hanjun
next prev parent reply other threads:[~2015-07-24 8:28 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 13:05 [PATCH v2 0/7] Making the generic ACPI GSI layer irqdomain aware Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` [PATCH v2 1/7] genirq: irqdomain: Use an accessor for the of_node field Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-24 8:54 ` Hanjun Guo
2015-07-24 8:54 ` Hanjun Guo
2015-07-24 17:06 ` Marc Zyngier
2015-07-24 17:06 ` Marc Zyngier
2015-07-23 13:05 ` [PATCH v2 2/7] genirq: irqdomain: Remove irqdomain dependency on struct device_node Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-24 9:08 ` Hanjun Guo
2015-07-24 9:08 ` Hanjun Guo
2015-07-23 13:05 ` [PATCH v2 3/7] genirq: irqdomain: Add irq_create_acpi_mapping Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-24 9:14 ` Hanjun Guo
2015-07-24 9:14 ` Hanjun Guo
2015-07-24 12:22 ` Marc Zyngier
2015-07-24 12:22 ` Marc Zyngier
2015-07-23 13:05 ` [PATCH v2 4/7] acpi: gsi: Always perform an irq domain lookup Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-24 8:34 ` Hanjun Guo
2015-07-24 8:34 ` Hanjun Guo
2015-07-23 13:05 ` [PATCH v2 5/7] acpi: gsi: Add acpi_set_irq_model to initialize the GSI layer Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-24 10:00 ` Hanjun Guo
2015-07-24 10:00 ` Hanjun Guo
2015-07-24 12:27 ` Marc Zyngier
2015-07-24 12:27 ` Marc Zyngier
2015-07-25 6:57 ` Hanjun Guo
2015-07-25 6:57 ` Hanjun Guo
2015-07-24 17:32 ` Lorenzo Pieralisi
2015-07-24 17:32 ` Lorenzo Pieralisi
2015-07-23 13:05 ` [PATCH v2 6/7] irqchip: GIC: Switch ACPI support to stacked domains Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-24 10:03 ` Hanjun Guo
2015-07-24 10:03 ` Hanjun Guo
2015-07-24 17:16 ` Lorenzo Pieralisi
2015-07-24 17:16 ` Lorenzo Pieralisi
2015-07-23 13:05 ` [PATCH v2 7/7] acpi: gsi: Cleanup acpi_register_gsi Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-23 13:05 ` Marc Zyngier
2015-07-24 10:06 ` Hanjun Guo
2015-07-24 10:06 ` Hanjun Guo
2015-07-24 16:17 ` Lorenzo Pieralisi
2015-07-24 16:17 ` Lorenzo Pieralisi
2015-07-24 8:27 ` Hanjun Guo [this message]
2015-07-24 8:27 ` [PATCH v2 0/7] Making the generic ACPI GSI layer irqdomain aware Hanjun Guo
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=55B1F708.3010804@linaro.org \
--to=hanjun.guo@linaro.org \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=graeme@xora.org.uk \
--cc=jason@lakedaemon.net \
--cc=jiang.liu@linux.intel.com \
--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=marc.zyngier@arm.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tomasz.nowicki@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.