[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2277339.U6fWlSIDzy@wuerfel>
Date: Fri, 18 Dec 2015 13:40:50 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Tomasz Nowicki <tn@...ihalf.com>, bhelgaas@...gle.com,
will.deacon@....com, catalin.marinas@....com, rjw@...ysocki.net,
hanjun.guo@...aro.org, Lorenzo.Pieralisi@....com,
okaya@...eaurora.org, jiang.liu@...ux.intel.com,
Stefano.Stabellini@...citrix.com, jchandra@...adcom.com,
jcm@...hat.com, linaro-acpi@...ts.linaro.org,
linux-pci@...r.kernel.org, Liviu.Dudau@....com,
ddaney@...iumnetworks.com, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, robert.richter@...iumnetworks.com,
Suravee.Suthikulpanit@....com, msalter@...hat.com,
wangyijing@...wei.com, tglx@...utronix.de, mw@...ihalf.com
Subject: Re: [PATCH V2 21/23] pci, acpi: Support for ACPI based PCI hostbridge init
On Wednesday 16 December 2015 16:16:31 Tomasz Nowicki wrote:
> Because of two patch series:
> 1. Jiang Liu's common interface to support PCI host bridge init
> 2. MMCONFIG refactoring (part of this patch set)
> now we can think about generic ACPI based PCI host bridge driver
> out of arch/ directory.
>
> This driver use information from MCFG table (PCI config space regions)
> and _CRS method (IO/irq resources) to initialize PCI hostbridge.
>
> TBD: We are still not sure whether we should reassign resources
> after PCI bus enumeration or trust firmware to do all that work for
> us properly.
>
> Signed-off-by: Tomasz Nowicki <tn@...ihalf.com>
> Signed-off-by: Hanjun Guo <hanjun.guo@...aro.org>
> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
> CC: Arnd Bergmann <arnd@...db.de>
> CC: Catalin Marinas <catalin.marinas@....com>
> CC: Liviu Dudau <Liviu.Dudau@....com>
> CC: Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>
> CC: Will Deacon <will.deacon@....com>
> Tested-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
>
I think this code could better live in drivers/acpi/pci_root.c
along with all the related functions. It's not really a driver
by itself and cannot be a loadable module or built on other
architectures.
You can put all the code inside an #ifdef ARCH_PCI_HOST_GENERIC_ACPI
there.
Arnd
--
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