From: Arnd Bergmann <arnd@arndb.de>
To: Dongdong Liu <liudongdong3@huawei.com>
Cc: helgaas@kernel.org, rafael@kernel.org, Lorenzo.Pieralisi@arm.com,
tn@semihalf.com, wangzhou1@hisilicon.com,
pratyush.anand@gmail.com, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
jcm@redhat.com, gabriele.paoloni@huawei.com,
charles.chenxin@huawei.com, linuxarm@huawei.com
Subject: Re: [RFC PATCH 3/3] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers
Date: Tue, 12 Jul 2016 10:35:15 +0200 [thread overview]
Message-ID: <3580311.QdyhSxNzVU@wuerfel> (raw)
In-Reply-To: <1468291344-122909-4-git-send-email-liudongdong3@huawei.com>
On Tuesday, July 12, 2016 10:42:24 AM CEST Dongdong Liu wrote:
> MAINTAINERS | 1 +
> drivers/pci/host/Kconfig | 7 ++
> drivers/pci/host/Makefile | 1 +
> drivers/pci/host/mcfg-quirks.c | 8 ++
> drivers/pci/host/mcfg-quirks.h | 8 ++
> drivers/pci/host/pcie-hisi-acpi.c | 151 ++++++++++++++++++++++++++++++++++++++
> drivers/pci/host/pcie-hisi.c | 2 -
> drivers/pci/host/pcie-hisi.h | 2 +
> 8 files changed, 178 insertions(+), 2 deletions(-)
> create mode 100644 drivers/pci/host/pcie-hisi-acpi.c
>
>
Please keep the quirks separate from the PCI host drivers.
The ACPI code includes its own host driver and the only thing
you need to override here is the config space access, so just put that
into drivers/acpi/
Arnd
next prev parent reply other threads:[~2016-07-12 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 2:42 [RFC PATCH 0/3] Add ACPI support for Hisilicon PCIe Host Controller Dongdong Liu
2016-07-12 2:42 ` [RFC PATCH 1/3] PCI: hisi: re-architect Hip05/Hip06 controllers driver to preapare for ACPI Dongdong Liu
2016-07-12 2:42 ` [RFC PATCH 2/3] PCI: hisi: Add ECAM support for devices that are not RC Dongdong Liu
2016-07-12 2:42 ` [RFC PATCH 3/3] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers Dongdong Liu
2016-07-12 8:35 ` Arnd Bergmann [this message]
2016-07-12 10:21 ` Gabriele Paoloni
2016-07-12 10:32 ` Gabriele Paoloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3580311.QdyhSxNzVU@wuerfel \
--to=arnd@arndb.de \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=charles.chenxin@huawei.com \
--cc=gabriele.paoloni@huawei.com \
--cc=helgaas@kernel.org \
--cc=jcm@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=pratyush.anand@gmail.com \
--cc=rafael@kernel.org \
--cc=tn@semihalf.com \
--cc=wangzhou1@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).