From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: linux-arm-kernel@lists.infradead.org, Adam Ford <aford173@gmail.com>
Cc: aford@beaconembedded.com, Adam Ford <aford173@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mp: Fix pgc vpu locations
Date: Thu, 20 Jun 2024 13:37:15 +0200 [thread overview]
Message-ID: <2295311.iZASKD2KPV@steina-w> (raw)
In-Reply-To: <20240619101045.6317-1-aford173@gmail.com>
Hi Adam,
Am Mittwoch, 19. Juni 2024, 12:10:44 CEST schrieb Adam Ford:
> The various pgv_vpu nodes have a mismatch between the value after
> the @ symbol and what is referenced by 'reg' so reorder the nodes
> to align.
>
> Fixes: df680992dd62 ("arm64: dts: imx8mp: add vpu pgc nodes")
> Suggested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> Signed-off-by: Adam Ford <aford173@gmail.com>
Thanks for the patch.
Reviewd-by: Alexander Stein <alexander.stein@ew.tq-group.com>
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> index 3576d2b89b43..ee0c864f27e8 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> @@ -838,6 +838,12 @@ pgc_gpumix: power-domain@7 {
> assigned-clock-rates = <800000000>, <400000000>;
> };
>
> + pgc_vpumix: power-domain@8 {
> + #power-domain-cells = <0>;
> + reg = <IMX8MP_POWER_DOMAIN_VPUMIX>;
> + clocks = <&clk IMX8MP_CLK_VPU_ROOT>;
> + };
> +
> pgc_gpu3d: power-domain@9 {
> #power-domain-cells = <0>;
> reg = <IMX8MP_POWER_DOMAIN_GPU3D>;
> @@ -853,6 +859,28 @@ pgc_mediamix: power-domain@10 {
> <&clk IMX8MP_CLK_MEDIA_APB_ROOT>;
> };
>
> + pgc_vpu_g1: power-domain@11 {
> + #power-domain-cells = <0>;
> + power-domains = <&pgc_vpumix>;
> + reg = <IMX8MP_POWER_DOMAIN_VPU_G1>;
> + clocks = <&clk IMX8MP_CLK_VPU_G1_ROOT>;
> + };
> +
> + pgc_vpu_g2: power-domain@12 {
> + #power-domain-cells = <0>;
> + power-domains = <&pgc_vpumix>;
> + reg = <IMX8MP_POWER_DOMAIN_VPU_G2>;
> + clocks = <&clk IMX8MP_CLK_VPU_G2_ROOT>;
> +
> + };
> +
> + pgc_vpu_vc8000e: power-domain@13 {
> + #power-domain-cells = <0>;
> + power-domains = <&pgc_vpumix>;
> + reg = <IMX8MP_POWER_DOMAIN_VPU_VC8000E>;
> + clocks = <&clk IMX8MP_CLK_VPU_VC8KE_ROOT>;
> + };
> +
> pgc_hdmimix: power-domain@14 {
> #power-domain-cells = <0>;
> reg = <IMX8MP_POWER_DOMAIN_HDMIMIX>;
> @@ -890,33 +918,6 @@ pgc_ispdwp: power-domain@18 {
> reg = <IMX8MP_POWER_DOMAIN_MEDIAMIX_ISPDWP>;
> clocks = <&clk IMX8MP_CLK_MEDIA_ISP_ROOT>;
> };
> -
> - pgc_vpumix: power-domain@19 {
> - #power-domain-cells = <0>;
> - reg = <IMX8MP_POWER_DOMAIN_VPUMIX>;
> - clocks = <&clk IMX8MP_CLK_VPU_ROOT>;
> - };
> -
> - pgc_vpu_g1: power-domain@20 {
> - #power-domain-cells = <0>;
> - power-domains = <&pgc_vpumix>;
> - reg = <IMX8MP_POWER_DOMAIN_VPU_G1>;
> - clocks = <&clk IMX8MP_CLK_VPU_G1_ROOT>;
> - };
> -
> - pgc_vpu_g2: power-domain@21 {
> - #power-domain-cells = <0>;
> - power-domains = <&pgc_vpumix>;
> - reg = <IMX8MP_POWER_DOMAIN_VPU_G2>;
> - clocks = <&clk IMX8MP_CLK_VPU_G2_ROOT>;
> - };
> -
> - pgc_vpu_vc8000e: power-domain@22 {
> - #power-domain-cells = <0>;
> - power-domains = <&pgc_vpumix>;
> - reg = <IMX8MP_POWER_DOMAIN_VPU_VC8000E>;
> - clocks = <&clk IMX8MP_CLK_VPU_VC8KE_ROOT>;
> - };
> };
> };
> };
>
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2024-06-20 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 10:10 [PATCH] arm64: dts: imx8mp: Fix pgc vpu locations Adam Ford
2024-06-20 11:37 ` Alexander Stein [this message]
2024-06-27 7:52 ` Shawn Guo
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=2295311.iZASKD2KPV@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).