From: Rob Herring <robh@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] PCI: Introduce UniPhier NX1 PCI endpoint controller support
Date: Wed, 9 Feb 2022 16:04:55 -0600 [thread overview]
Message-ID: <YgQ6h3qYxWUiLWZ0@robh.at.kernel.org> (raw)
In-Reply-To: <1643948739-14889-1-git-send-email-hayashi.kunihiko@socionext.com>
On Fri, Feb 04, 2022 at 01:25:36PM +0900, Kunihiko Hayashi wrote:
> This series includes the patches to add basic support for the PCI endpoint
> controller implemented in NX1 SoC.
>
> Existing functions for Pro5 treat as "legacy" because the some registers
> and initialization of NX1 is different from Pro5.
>
> Changes since v1:
> - Fix dt-bindings warnings
>
> Kunihiko Hayashi (3):
> dt-bindings: PCI: uniphier-ep: Add bindings for NX1 SoC
> PCI: uniphier-ep: Add support for non-legacy SoC
> PCI: uniphier-ep: Add compatible string and SoC-dependent data for NX1
> SoC
>
> .../bindings/pci/socionext,uniphier-pcie-ep.yaml | 22 ++--
> drivers/pci/controller/dwc/pcie-uniphier-ep.c | 139 ++++++++++++++++++---
> 2 files changed, 136 insertions(+), 25 deletions(-)
For the series:
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2022-02-09 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 4:25 [PATCH v2 0/3] PCI: Introduce UniPhier NX1 PCI endpoint controller support Kunihiko Hayashi
2022-02-04 4:25 ` [PATCH v2 1/3] dt-bindings: PCI: uniphier-ep: Add bindings for NX1 SoC Kunihiko Hayashi
2022-02-04 4:25 ` [PATCH v2 2/3] PCI: uniphier-ep: Add support for non-legacy SoC Kunihiko Hayashi
2022-02-04 4:25 ` [PATCH v2 3/3] PCI: uniphier-ep: Add compatible string and SoC-dependent data for NX1 SoC Kunihiko Hayashi
2022-02-09 22:04 ` Rob Herring [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=YgQ6h3qYxWUiLWZ0@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mhiramat@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).