From: ddaney.cavm@gmail.com (David Daney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] pci: Add host controller driver for Cavium ThunderX PCIe
Date: Tue, 22 Dec 2015 15:43:50 -0800 [thread overview]
Message-ID: <1450827832-3294-1-git-send-email-ddaney.cavm@gmail.com> (raw)
From: David Daney <david.daney@cavium.com>
Some Cavium ThunderX processors require quirky access methods for the
config space of the PCIe bridge.
There are two patches:
1) Refactor code in pci-host-generic so that it can more easily be
used by other drivers. This splits the driver for CAM and ECAM
access methods to a separate file from the common host driver code.
2) Add the ThunderX PCIe driver, which leverages the code in
pci-host-generic
Changes from v1: Split CAM and ECAM code from common driver code as
suggested by Arnd Bergmann. Fix spelling errors in
pcie-thunder-pem.txt
David Daney (2):
PCI: generic: Refactor code to enable reuse by other drivers.
pci, pcie-thunder-pem: Add PCIe host driver for ThunderX processors.
.../devicetree/bindings/pci/pcie-thunder-pem.txt | 43 ++++
drivers/pci/host/Kconfig | 11 +
drivers/pci/host/Makefile | 2 +
drivers/pci/host/pci-host-common.c | 194 ++++++++++++++
drivers/pci/host/pci-host-common.h | 56 ++++
drivers/pci/host/pci-host-generic.c | 190 +-------------
drivers/pci/host/pcie-thunder-pem.c | 283 +++++++++++++++++++++
7 files changed, 593 insertions(+), 186 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pci/pcie-thunder-pem.txt
create mode 100644 drivers/pci/host/pci-host-common.c
create mode 100644 drivers/pci/host/pci-host-common.h
create mode 100644 drivers/pci/host/pcie-thunder-pem.c
--
1.8.3.1
next reply other threads:[~2015-12-22 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 23:43 David Daney [this message]
2015-12-22 23:43 ` [PATCH v2 1/2] PCI: generic: Refactor code to enable reuse by other drivers David Daney
2015-12-22 23:43 ` [PATCH v2 2/2] pci, pcie-thunder-pem: Add PCIe host driver for ThunderX processors David Daney
2015-12-29 20:37 ` Rob Herring
2016-01-04 18:18 ` David Daney
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=1450827832-3294-1-git-send-email-ddaney.cavm@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).