From: Bjorn Helgaas <helgaas@kernel.org>
To: Ray Jui <ray.jui@broadcom.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
Alex Barba <alex.barba@broadcom.com>,
Oza Oza <oza.oza@broadcom.com>, Ray Jui <rjui@broadcom.com>
Subject: Re: [PATCH 00/12] Additional iProc PCIe host support/fixes
Date: Mon, 24 Oct 2016 17:52:38 -0500 [thread overview]
Message-ID: <20161024225238.GA27451@localhost> (raw)
In-Reply-To: <1477347432-17656-1-git-send-email-ray.jui@broadcom.com>
Hi Ray,
On Mon, Oct 24, 2016 at 03:17:00PM -0700, Ray Jui wrote:
> This patch series contains various changes and fixes to the iProc PCIe
> host driver. It also adds support for the next generation of PAXB and
> PAXC based host controllers
>
> This patch series was developed based on v4.9-rc1 and tested on both NS2
> SVK and Cygnus wireless audio platform
>
> repo: https://github.com/Broadcom/arm64-linux.git
> branch: iproc-pcie-v1
>
> Ray Jui (12):
> PCI: iproc: Improve core register population
> PCI: iproc: Do not reset PAXC when initializing the driver
> PCI: iproc: Add BCMA type
> PCI: iproc: Fix exception with multi-function devices
> PCI: iproc: Update iProc PCIe DT binding
> PCI: iproc: Add PAXC v2 support
> PCI: iproc: Update iProc PCIe DT binding
> PCI: iproc: Making outbound mapping code more generic
> PCI: iproc: Update iProc PCIe DT binding
> PCI: iproc: Add inbound DMA mapping support
> PCI: iproc: Update iProc PCIe DT binding
> PCI: iproc: Add support for the next-gen PAXB controller
I'll look at these more soon, but there are four patches above with
identical titles ("PCI: iproc: Update iProc PCIe DT binding"). The
"iProc PCIe" part is a little redundant; can you remove that and
instead include a hint about what each patch is about, e.g.,
"add optional dma-ranges", "remove outbound window properties", etc?
> .../devicetree/bindings/pci/brcm,iproc-pcie.txt | 43 +-
> drivers/pci/host/pcie-iproc-bcma.c | 1 +
> drivers/pci/host/pcie-iproc-msi.c | 1 +
> drivers/pci/host/pcie-iproc-platform.c | 19 +-
> drivers/pci/host/pcie-iproc.c | 942 ++++++++++++++++++---
> drivers/pci/host/pcie-iproc.h | 45 +-
> 6 files changed, 916 insertions(+), 135 deletions(-)
>
> --
> 2.1.4
>
next prev parent reply other threads:[~2016-10-24 22:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 22:17 [PATCH 00/12] Additional iProc PCIe host support/fixes Ray Jui
2016-10-24 22:17 ` [PATCH 01/12] PCI: iproc: Improve core register population Ray Jui
2016-10-24 22:17 ` [PATCH 02/12] PCI: iproc: Do not reset PAXC when initializing the driver Ray Jui
2016-10-24 22:17 ` [PATCH 03/12] PCI: iproc: Add BCMA type Ray Jui
2016-10-24 22:17 ` [PATCH 04/12] PCI: iproc: Fix exception with multi-function devices Ray Jui
2016-10-24 22:17 ` [PATCH 05/12] PCI: iproc: Update iProc PCIe DT binding Ray Jui
2016-10-24 22:17 ` [PATCH 06/12] PCI: iproc: Add PAXC v2 support Ray Jui
2016-10-24 22:17 ` [PATCH 07/12] PCI: iproc: Update iProc PCIe DT binding Ray Jui
2016-10-24 22:24 ` Scott Branden
2016-10-24 22:27 ` Ray Jui
2016-10-24 22:17 ` [PATCH 08/12] PCI: iproc: Making outbound mapping code more generic Ray Jui
2016-10-24 22:17 ` [PATCH 09/12] PCI: iproc: Update iProc PCIe DT binding Ray Jui
2016-10-24 22:17 ` [PATCH 10/12] PCI: iproc: Add inbound DMA mapping support Ray Jui
2016-10-24 22:17 ` [PATCH 11/12] PCI: iproc: Update iProc PCIe DT binding Ray Jui
2016-10-24 22:17 ` [PATCH 12/12] PCI: iproc: Add support for the next-gen PAXB controller Ray Jui
2016-10-24 22:30 ` [PATCH 00/12] Additional iProc PCIe host support/fixes Scott Branden
2016-10-24 22:31 ` Ray Jui
2016-10-24 22:52 ` Bjorn Helgaas [this message]
2016-10-24 22:54 ` Ray Jui
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=20161024225238.GA27451@localhost \
--to=helgaas@kernel.org \
--cc=alex.barba@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=oza.oza@broadcom.com \
--cc=ray.jui@broadcom.com \
--cc=rjui@broadcom.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).