From: Bjorn Helgaas <helgaas@kernel.org>
To: Tomasz Nowicki <tn@semihalf.com>
Cc: rafael@kernel.org, linux-pci@vger.kernel.org,
will.deacon@arm.com, okaya@codeaurora.org, wangyijing@huawei.com,
andrea.gallo@linaro.org, Lorenzo.Pieralisi@arm.com,
linaro-acpi@lists.linaro.org, ddaney@caviumnetworks.com,
linux-acpi@vger.kernel.org, robert.richter@caviumnetworks.com,
liudongdong3@huawei.com, catalin.marinas@arm.com,
Liviu.Dudau@arm.com, arnd@arndb.de, jcm@redhat.com,
msalter@redhat.com, cov@codeaurora.org, mw@semihalf.com,
linux-arm-kernel@lists.infradead.org, jchandra@broadcom.com,
dhdang@apm.com, linux-kernel@vger.kernel.org,
jeremy.linton@arm.com, hanjun.guo@linaro.org,
Suravee.Suthikulpanit@amd.com
Subject: Re: [RFC PATCH 0/3] ECAM quirks handling for ARM64 platforms
Date: Tue, 19 Jul 2016 16:17:53 -0500 [thread overview]
Message-ID: <20160719211753.GA17840@localhost> (raw)
In-Reply-To: <1464856864-18049-1-git-send-email-tn@semihalf.com>
On Thu, Jun 02, 2016 at 10:41:00AM +0200, Tomasz Nowicki wrote:
> This series bases on pending ACPI PCI support for ARM64:
> https://lkml.org/lkml/2016/5/30/468
>
> Quirk handling relies on an idea of matching MCFG OEM ID and OEM revision
> (the ones from standard header of MCFG table). Linker section is used
> so that quirks can be registered using special macro (see patches) and
> kept self contained.
>
> As an example, last patch presents above mechanism usage for ThunderX PEM driver.
>
> Tomasz Nowicki (3):
> pci, acpi: Match PCI config space accessors against platfrom specific
> ECAM quirks.
> arm64, pci: Start using quirks handling for ACPI based PCI host
> controller.
> pci, pci-thunder-pem: Add ACPI support for ThunderX PEM.
>
> arch/arm64/kernel/pci.c | 7 +-
> drivers/acpi/pci_mcfg.c | 32 +++++++++
> drivers/pci/host/pci-thunder-pem.c | 132 +++++++++++++++++++++++++++++++++----
> include/asm-generic/vmlinux.lds.h | 7 ++
> include/linux/pci-acpi.h | 19 ++++++
> 5 files changed, 181 insertions(+), 16 deletions(-)
Is this series superceded by Dongdong's series of 6/13 ("[RFC,V2,1/2]
ACPI/PCI: Match PCI config space accessors against platfrom specific ECAM
quirks")?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-07-19 21:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 8:41 [RFC PATCH 0/3] ECAM quirks handling for ARM64 platforms Tomasz Nowicki
2016-06-02 8:41 ` [RFC PATCH 1/3] pci, acpi: Match PCI config space accessors against platfrom specific ECAM quirks Tomasz Nowicki
2016-06-02 11:42 ` Arnd Bergmann
2016-06-02 12:07 ` Tomasz Nowicki
2016-06-02 12:32 ` Arnd Bergmann
2016-06-02 13:35 ` Tomasz Nowicki
2016-06-02 15:19 ` Arnd Bergmann
2016-06-14 9:06 ` Tomasz Nowicki
2016-06-03 15:15 ` Christopher Covington
2016-06-03 15:32 ` Gabriele Paoloni
2016-06-03 16:57 ` David Daney
2016-06-03 16:59 ` Jeffrey Hugo
2016-06-06 7:27 ` Gabriele Paoloni
2016-06-06 7:54 ` Hanjun Guo
2016-06-02 8:41 ` [RFC PATCH 2/3] arm64, pci: Start using quirks handling for ACPI based PCI host controller Tomasz Nowicki
2016-06-02 8:41 ` [RFC PATCH 3/3] pci, pci-thunder-pem: Add ACPI support for ThunderX PEM Tomasz Nowicki
2016-07-19 21:17 ` Bjorn Helgaas [this message]
2016-07-20 5:05 ` [RFC PATCH 0/3] ECAM quirks handling for ARM64 platforms Tomasz Nowicki
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=20160719211753.GA17840@localhost \
--to=helgaas@kernel.org \
--cc=Liviu.Dudau@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=andrea.gallo@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cov@codeaurora.org \
--cc=ddaney@caviumnetworks.com \
--cc=dhdang@apm.com \
--cc=hanjun.guo@linaro.org \
--cc=jchandra@broadcom.com \
--cc=jcm@redhat.com \
--cc=jeremy.linton@arm.com \
--cc=linaro-acpi@lists.linaro.org \
--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=liudongdong3@huawei.com \
--cc=msalter@redhat.com \
--cc=mw@semihalf.com \
--cc=okaya@codeaurora.org \
--cc=rafael@kernel.org \
--cc=robert.richter@caviumnetworks.com \
--cc=tn@semihalf.com \
--cc=wangyijing@huawei.com \
--cc=will.deacon@arm.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).