Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755009AbcKVHoF convert rfc822-to-8bit (ORCPT ); Tue, 22 Nov 2016 02:44:05 -0500 Received: from lhrrgout.huawei.com ([194.213.3.17]:4245 "EHLO lhrrgout.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752756AbcKVHoD (ORCPT ); Tue, 22 Nov 2016 02:44:03 -0500 From: Gabriele Paoloni To: Bjorn Helgaas CC: "liudongdong (C)" , "arnd@arndb.de" , "rafael@kernel.org" , "Lorenzo.Pieralisi@arm.com" , "tn@semihalf.com" , "Wangzhou (B)" , "pratyush.anand@gmail.com" , "linux-pci@vger.kernel.org" , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "jcm@redhat.com" , "Chenxin (Charles)" , "hanjun.guo@linaro.org" , Linuxarm Subject: RE: [PATCH V5 2/2] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers Thread-Topic: [PATCH V5 2/2] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers Thread-Index: AQHSQXr341aGNHD/0ESLt0D5n3bFe6De+cSAgAQvEzCAAOJHgIAAmhYg Date: Tue, 22 Nov 2016 07:43:39 +0000 Message-ID: References: <1479460951-49281-1-git-send-email-liudongdong3@huawei.com> <1479460951-49281-3-git-send-email-liudongdong3@huawei.com> <20161118170821.GH25762@bhelgaas-glaptop.roam.corp.google.com> <20161121223145.GC4832@bhelgaas-glaptop.roam.corp.google.com> In-Reply-To: <20161121223145.GC4832@bhelgaas-glaptop.roam.corp.google.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.203.181.151] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.5833F739.00BB,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 7d9e522cb8436fae0e56456607513c68 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2125 Lines: 57 > -----Original Message----- > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > Sent: 21 November 2016 22:32 > To: Gabriele Paoloni > Cc: liudongdong (C); arnd@arndb.de; rafael@kernel.org; > Lorenzo.Pieralisi@arm.com; tn@semihalf.com; Wangzhou (B); > pratyush.anand@gmail.com; linux-pci@vger.kernel.org; linux- > acpi@vger.kernel.org; linux-kernel@vger.kernel.org; jcm@redhat.com; > Chenxin (Charles); hanjun.guo@linaro.org; Linuxarm > Subject: Re: [PATCH V5 2/2] PCI/ACPI: hisi: Add ACPI support for > HiSilicon SoCs Host Controllers > > On Mon, Nov 21, 2016 at 09:09:28AM +0000, Gabriele Paoloni wrote: > > > > > +config PCI_HISI_ACPI > > > > + depends on ACPI && ARM64 > > > > + bool "HiSilicon Hip05 and Hip06 and Hip07 SoCs ACPI PCIe > > > controllers" > > > > + select PNP > > > > + help > > > > + Say Y here if you want ACPI PCIe controller support on > > > HiSilicon > > > > + Hip05 and Hip06 and Hip07 SoCs > > > > > > I'm not sure about this Kconfig setup. Do we really want to force > > > people to enable a special config option to get this support? > > > > > > I'm comparing it in my mind with other PCI quirks. They're all > > > enabled as a group by CONFIG_PCI_QUIRKS. Ultimately we want an > ACPI > > > kernel to work without requiring any platform-specific config > options. > > > > > > I'm wondering if we should consolidate all the ECAM quirk code in a > > > single place (maybe pci/ecam-quirks.c, pci/ecam.c, or pci/pci- > acpi.c), > > > under a config option like CONFIG_PCI_ECAM_QUIRKS or maybe even > plain > > > CONFIG_PCI_QUIRKS (of course, it could still be qualified by > > > CONFIG_ACPI and CONFIG_ARM64). > > > > What about having a single config options but keeping separate files > > for each vendors (at least as first step)? > > That sounds fine. The main thing is that we're trying to build a > generic kernel that can run on any ACPI arm64 platform, so we really > shouldn't have to turn on platform-specific config options. Ok great we'll do so then Thanks Gab > > > Maybe if we see that we can consolidate all the vendors in one file > > we can do it as a second step...