From: Arnd Bergmann <arnd@arndb.de>
To: Gabriele Paoloni <gabriele.paoloni@huawei.com>
Cc: guohanjun@huawei.com, wangzhou1@hisilicon.com,
liudongdong3@huawei.com, linuxarm@huawei.com,
qiujiang@huawei.com, bhelgaas@google.com,
Lorenzo.Pieralisi@arm.com, tn@semihalf.com,
zhangjukuo@huawei.com, xuwei5@hisilicon.com,
liguozhu@hisilicon.com, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, jcm@redhat.com
Subject: Re: [RFC PATCH 0/4] Add ACPI support for HiSilicon PCIe Host Controllers
Date: Thu, 04 Feb 2016 14:11:32 +0100 [thread overview]
Message-ID: <2387127.DMZaDnZvEW@wuerfel> (raw)
In-Reply-To: <1454585860-60709-1-git-send-email-gabriele.paoloni@huawei.com>
On Thursday 04 February 2016 19:37:36 Gabriele Paoloni wrote:
> From: gabriele paoloni <gabriele.paoloni@huawei.com>
>
> This patchset adds ACPI support for the HiSilicon Hip05/Hip06 SoC PCIe controllers
> The four patches respectively:
> - rework PCie Designware to be used for ACPI PCI Host controllers
> - re-architect the current HiSilicon driver to make it scalable to the
> new ACPI quirks
> - rework the current HiSilicon driver to make it ECAM compliant
> - adds the HiSilicon ACPI specific quirks.
>
> This patchset is based on
> https://github.com/semihalf-nowicki-tomasz/linux.git
> branch pci-acpi-v3 + Hip06 support applied on top:
> https://patchwork.ozlabs.org/patch/549198/
>
ACPI has its own PCI support, and should not need drivers for host
bridges. I don't think we can really mix the two things, as ACPI
needs to have access to things like PCI config space way before
we are probing normal device drivers.
Please put this in drivers/acpi/pci*.c.
Arnd
next prev parent reply other threads:[~2016-02-04 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 11:37 [RFC PATCH 0/4] Add ACPI support for HiSilicon PCIe Host Controllers Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 1/4] PCI: Designware: Add support for ACPI based controllers Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 2/4] PCI: hisi: re-architect Hip05/Hip06 controllers driver to preapare for ACPI Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 3/4] PCI: hisi: Make the HiSilicon PCIe host controller ECAM compliant Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 4/4] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers Gabriele Paoloni
2016-02-04 13:11 ` Arnd Bergmann [this message]
2016-02-04 15:11 ` [RFC PATCH 0/4] Add ACPI support for HiSilicon PCIe " Gabriele Paoloni
2016-02-04 16:07 ` Arnd Bergmann
2016-02-04 16:44 ` Gabriele Paoloni
2016-02-04 17:01 ` Arnd Bergmann
2016-02-04 17:06 ` Gabriele Paoloni
2016-02-08 13:17 ` Gabriele Paoloni
2016-02-08 13:55 ` Arnd Bergmann
2016-02-08 14:11 ` Sinan Kaya
2016-02-08 16:20 ` 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=2387127.DMZaDnZvEW@wuerfel \
--to=arnd@arndb.de \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=gabriele.paoloni@huawei.com \
--cc=guohanjun@huawei.com \
--cc=jcm@redhat.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=qiujiang@huawei.com \
--cc=tn@semihalf.com \
--cc=wangzhou1@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangjukuo@huawei.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).