From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: renesas: r8a779g0: Add FCPVX instances
Date: Wed, 18 Dec 2024 01:30:54 +0200 [thread overview]
Message-ID: <20241217233054.GP23470@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20241217-rcar-v4h-vspx-v1-2-de04ea044ed4@ideasonboard.com>
Hi Jacopo,
Thank you for the patch.
On Tue, Dec 17, 2024 at 06:53:15PM +0100, Jacopo Mondi wrote:
> Add device nodes for the FCPVX instances on R-Car V4H (R8A779G0) SoC.
>
> Signed-off-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> ---
> arch/arm64/boot/dts/renesas/r8a779g0.dtsi | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a779g0.dtsi b/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> index 61c6b8022ffdc3b22444fb13e748b4aaebe454a4..e49748563e2f5706ed982d6c9cc1df59f27bd0dc 100644
> --- a/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a779g0.dtsi
> @@ -2171,6 +2171,24 @@ fcpvd1: fcp@fea11000 {
> iommus = <&ipmmu_vi1 7>;
> };
>
> + fcpvx0: fcp@fedb0000 {
Please sort the nodes by unit address.
Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> + compatible = "renesas,fcpv";
> + reg = <0 0xfedb0000 0 0x200>;
> + clocks = <&cpg CPG_MOD 1100>;
> + power-domains = <&sysc R8A779G0_PD_ALWAYS_ON>;
> + resets = <&cpg 1100>;
> + iommus = <&ipmmu_vi1 24>;
> + };
> +
> + fcpvx1: fcp@fedb8000 {
> + compatible = "renesas,fcpv";
> + reg = <0 0xfedb8000 0 0x200>;
> + clocks = <&cpg CPG_MOD 1101>;
> + power-domains = <&sysc R8A779G0_PD_ALWAYS_ON>;
> + resets = <&cpg 1101>;
> + iommus = <&ipmmu_vi1 25>;
> + };
> +
> vspd0: vsp@fea20000 {
> compatible = "renesas,vsp2";
> reg = <0 0xfea20000 0 0x7000>;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-12-17 23:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 17:53 [PATCH 0/4] renesas: r8a779g0: Enable VSPX on R-Car V4H Jacopo Mondi
2024-12-17 17:53 ` [PATCH 1/4] clk: renesas: r8a779g0: Add FCPVX clocks Jacopo Mondi
2024-12-17 23:46 ` Laurent Pinchart
2024-12-18 8:53 ` Jacopo Mondi
2024-12-17 17:53 ` [PATCH 2/4] arm64: dts: renesas: r8a779g0: Add FCPVX instances Jacopo Mondi
2024-12-17 23:30 ` Laurent Pinchart [this message]
2024-12-17 17:53 ` [PATCH 3/4] clk: renesas: r8a779g0: Add VSPX clocks Jacopo Mondi
2024-12-17 23:47 ` Laurent Pinchart
2024-12-17 17:53 ` [PATCH 4/4] arm64: dts: renesas: r8a779g0: Add VSPX instances Jacopo Mondi
2024-12-17 23:42 ` Laurent Pinchart
2024-12-18 8:43 ` Jacopo Mondi
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=20241217233054.GP23470@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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