Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754854AbbDKMSs (ORCPT ); Sat, 11 Apr 2015 08:18:48 -0400 Received: from inca-roads.misterjones.org ([213.251.177.50]:43560 "EHLO inca-roads.misterjones.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752035AbbDKMSq (ORCPT ); Sat, 11 Apr 2015 08:18:46 -0400 X-Greylist: delayed 717 seconds by postgrey-1.27 at vger.kernel.org; Sat, 11 Apr 2015 08:18:46 EDT To: Feng Kan Subject: Re: [PATCH v3 1/4] PCI: X-Gene: Add the APM X-Gene v1 PCIe MSI/MSIX termination driver X-PHP-Originating-Script: 0:main.inc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 11 Apr 2015 13:18:43 +0100 From: Marc Zyngier Cc: "Rafael J. Wysocki" , Arnd Bergmann , , Duc Dang , Liviu Dudau , , , Tanmay Inamdar , Bjorn Helgaas , , Loc Ho Organization: ARM Ltd In-Reply-To: References: <20150408084448.5f0793b7@why.wild-wind.fr.eu.org> <7923ef6ffd60a7c3de3c8c04fe746bbd3c15b5ac.1428564115.git.dhdang@apm.com> <55280665.9020603@arm.com> Message-ID: User-Agent: Roundcube Webmail/0.7.2 X-SA-Exim-Connect-IP: X-SA-Exim-Rcpt-To: fkan@apm.com, rjw@rjwysocki.net, arnd@arndb.de, linux-pci@vger.kernel.org, dhdang@apm.com, liviu.dudau@arm.com, linux-kernel@vger.kernel.org, grant.likely@linaro.org, tinamdar@apm.com, bhelgaas@google.com, linux-arm-kernel@lists.infradead.org, lho@apm.com X-SA-Exim-Mail-From: marc.zyngier@arm.com X-SA-Exim-Scanned: No (on cheepnis.misterjones.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1316 Lines: 42 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/