From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.126.187]:49160 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751560AbbDKOu7 (ORCPT ); Sat, 11 Apr 2015 10:50:59 -0400 From: Arnd Bergmann To: Feng Kan Cc: Marc Zyngier , "Rafael J. Wysocki" , Duc Dang , Bjorn Helgaas , "grant.likely@linaro.org" , Liviu Dudau , "linux-pci@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Tanmay Inamdar , Loc Ho Subject: Re: [PATCH v3 1/4] PCI: X-Gene: Add the APM X-Gene v1 PCIe MSI/MSIX termination driver Date: Sat, 11 Apr 2015 16:50:47 +0200 Message-ID: <8653876.C24YDfhd04@wuerfel> In-Reply-To: References: <20150408084448.5f0793b7@why.wild-wind.fr.eu.org> <55280665.9020603@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: linux-pci-owner@vger.kernel.org List-ID: On Friday 10 April 2015 17:16:32 Feng Kan wrote: > Hi Marc: > > 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. > > Sorry for top posting. Doing gicv2m in ACPI should be straightforward, and the ACPI code can simply assume that there is only one GIC instance (whichever version) in the system and use that for all standard PCI hosts. Arnd