[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb00880b6d37fff304797d0c3e4e670d@www.loen.fr>
Date: Sat, 11 Apr 2015 13:18:43 +0100
From: Marc Zyngier <marc.zyngier@....com>
To: Feng Kan <fkan@....com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Arnd Bergmann <arnd@...db.de>, <linux-pci@...r.kernel.org>,
Duc Dang <dhdang@....com>, Liviu Dudau <liviu.dudau@....com>,
<linux-kernel@...r.kernel.org>, <grant.likely@...aro.org>,
Tanmay Inamdar <tinamdar@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
<linux-arm-kernel@...ts.infradead.org>, Loc Ho <lho@....com>
Subject: Re: [PATCH v3 1/4] PCI: X-Gene: Add the APM X-Gene v1 PCIe MSI/MSIX termination driver
Hi Feng,
On 2015-04-11 01:16, Feng Kan wrote:
> Is there any plans to support ACPI for GICv2m MSI? Both this driver
> and the
> GICv2m seems to support OF model of discovery for msi controller.
> X-Gene1
> uses this driver and X-Gene2 uses GICv2m, there needs to be a way to
> associate msi controller with the PCIe bus. I haven't
> found a standard way of doing finding "msi-parent" for ACPI. Do you
> have
> any suggestion.
This is remarkably off topic! ;-)
ACPI only provides information for GICv2m and GICv3. No other interrupt
controller,
MSI widget or fairy dust provider will be supported on arm64 with ACPI.
So this driver
will be DT only.
GICv2m, being described in the ACPI spec, is growing some support. My
understanding is
that this is done by AMD (Suravee Suthikulpanit) using my
irq/msi-domain branch as a
base (I know that Suravee is looking at expanding the irqdomain
matching code to
accept a pointer to an ACPI table instead of a device node to match the
target
domain).
Hope this helps,
M.
--
Fast, cheap, reliable. Pick two.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists