From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Jingoo Han <jingoohan1@gmail.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Murali Karicheri <m-karicheri2@ti.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH v3 0/4] PCI: dwc: Move iATU register mapping to common framework
Date: Thu, 8 Oct 2020 12:23:14 +0100 [thread overview]
Message-ID: <20201008112314.GA1181@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <1601444167-11316-1-git-send-email-hayashi.kunihiko@socionext.com>
On Wed, Sep 30, 2020 at 02:36:03PM +0900, Kunihiko Hayashi wrote:
> This moves iATU register mapping in the Keystone driver to common
> framework. And this adds "iatu" property description to the dt-bindings
> for UniPhier PCIe host and endpoint controller.
>
> This series is split from the previous patches:
> https://www.spinics.net/lists/linux-pci/msg97608.html
> "[PATCH v6 0/6] PCI: uniphier: Add features for UniPhier PCIe host controller"
>
> This has been confirmed with PCIe version 4.80 controller on UniPhier platform.
> Please comfirm this series on Keystone platform if necessary.
>
> Changes since v2:
> - dt-bindings: Fix errors from dt_binding_check
>
> Changes since v1:
> - Use to_platform_device() instead of of_find_device_by_node()
> - Add Reviewed-by: line to 4th patch for keystone
> - dt-bindings: Add description for uniphier-ep
>
> Kunihiko Hayashi (4):
> dt-bindings: PCI: uniphier: Add iATU register description
> dt-bindings: PCI: uniphier-ep: Add iATU register description
> PCI: dwc: Add common iATU register support
> PCI: keystone: Remove iATU register mapping
>
> .../bindings/pci/socionext,uniphier-pcie-ep.yaml | 20 ++++++++++++++------
> .../devicetree/bindings/pci/uniphier-pcie.txt | 1 +
> drivers/pci/controller/dwc/pci-keystone.c | 20 ++++----------------
> drivers/pci/controller/dwc/pcie-designware.c | 5 +++++
> 4 files changed, 24 insertions(+), 22 deletions(-)
Applied to pci/dwc, thanks.
Lorenzo
prev parent reply other threads:[~2020-10-08 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 5:36 [PATCH v3 0/4] PCI: dwc: Move iATU register mapping to common framework Kunihiko Hayashi
2020-09-30 5:36 ` [PATCH v3 1/4] dt-bindings: PCI: uniphier: Add iATU register description Kunihiko Hayashi
2020-09-30 5:36 ` [PATCH v3 2/4] dt-bindings: PCI: uniphier-ep: " Kunihiko Hayashi
2020-09-30 12:48 ` Rob Herring
2020-09-30 5:36 ` [PATCH v3 3/4] PCI: dwc: Add common iATU register support Kunihiko Hayashi
2020-09-30 12:49 ` Rob Herring
2020-09-30 5:36 ` [PATCH v3 4/4] PCI: keystone: Remove iATU register mapping Kunihiko Hayashi
2020-10-08 11:23 ` Lorenzo Pieralisi [this message]
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=20201008112314.GA1181@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=jingoohan1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=masami.hiramatsu@linaro.org \
--cc=robh+dt@kernel.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).