From: Masahiro Yamada <masahiroy@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Rob Herring <robh+dt@kernel.org>,
DTML <devicetree@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: uniphier: Add PCIe endpoint and PHY node for Pro5
Date: Fri, 10 Jul 2020 10:49:21 +0900 [thread overview]
Message-ID: <CAK7LNASAvC2aF9530Dc24dcVfVH_SK3ZpdkjSmSEj9xw+mXr6A@mail.gmail.com> (raw)
In-Reply-To: <1594198320-28900-1-git-send-email-hayashi.kunihiko@socionext.com>
On Wed, Jul 8, 2020 at 5:52 PM Kunihiko Hayashi
<hayashi.kunihiko@socionext.com> wrote:
>
> This adds PCIe endpoint controller and PHY nodes for Pro5 SoC,
> and also adds pinctrl node for PCIe.
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Applied.
> ---
> arch/arm/boot/dts/uniphier-pinctrl.dtsi | 5 +++++
> arch/arm/boot/dts/uniphier-pro5.dtsi | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 35 insertions(+)
>
> diff --git a/arch/arm/boot/dts/uniphier-pinctrl.dtsi b/arch/arm/boot/dts/uniphier-pinctrl.dtsi
> index bfdfb76..c0fd029 100644
> --- a/arch/arm/boot/dts/uniphier-pinctrl.dtsi
> +++ b/arch/arm/boot/dts/uniphier-pinctrl.dtsi
> @@ -126,6 +126,11 @@
> function = "nand";
> };
>
> + pinctrl_pcie: pcie {
> + groups = "pcie";
> + function = "pcie";
> + };
> +
> pinctrl_sd: sd {
> groups = "sd";
> function = "sd";
> diff --git a/arch/arm/boot/dts/uniphier-pro5.dtsi b/arch/arm/boot/dts/uniphier-pro5.dtsi
> index feadb4a..3525125 100644
> --- a/arch/arm/boot/dts/uniphier-pro5.dtsi
> +++ b/arch/arm/boot/dts/uniphier-pro5.dtsi
> @@ -613,6 +613,36 @@
> };
> };
>
> + pcie_ep: pcie-ep@66000000 {
> + compatible = "socionext,uniphier-pro5-pcie-ep",
> + "snps,dw-pcie-ep";
> + status = "disabled";
> + reg-names = "dbi", "dbi2", "link", "addr_space";
> + reg = <0x66000000 0x1000>, <0x66001000 0x1000>,
> + <0x66010000 0x10000>, <0x67000000 0x400000>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_pcie>;
> + clock-names = "gio", "link";
> + clocks = <&sys_clk 12>, <&sys_clk 24>;
> + reset-names = "gio", "link";
> + resets = <&sys_rst 12>, <&sys_rst 24>;
> + num-ib-windows = <16>;
> + num-ob-windows = <16>;
> + num-lanes = <4>;
> + phy-names = "pcie-phy";
> + phys = <&pcie_phy>;
> + };
> +
> + pcie_phy: phy@66038000 {
> + compatible = "socionext,uniphier-pro5-pcie-phy";
> + reg = <0x66038000 0x4000>;
> + #phy-cells = <0>;
> + clock-names = "gio", "link";
> + clocks = <&sys_clk 12>, <&sys_clk 24>;
> + reset-names = "gio", "link";
> + resets = <&sys_rst 12>, <&sys_rst 24>;
> + };
> +
> nand: nand-controller@68000000 {
> compatible = "socionext,uniphier-denali-nand-v5b";
> status = "disabled";
> --
> 2.7.4
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2020-07-10 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 8:52 [PATCH] ARM: dts: uniphier: Add PCIe endpoint and PHY node for Pro5 Kunihiko Hayashi
2020-07-10 1:49 ` Masahiro Yamada [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=CAK7LNASAvC2aF9530Dc24dcVfVH_SK3ZpdkjSmSEj9xw+mXr6A@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).