devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitor Soares <ivitro@gmail.com>
To: Peng Fan <peng.fan@nxp.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>,
	Ulf Hansson <ulf.hansson@linaro.org>
Cc: Vitor Soares <vitor.soares@toradex.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	 "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	 Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH v1] arm64: dts: imx8mp: Fix VPU PGC power-domain parents
Date: Tue, 02 Jul 2024 21:32:48 +0100	[thread overview]
Message-ID: <4b2da701dd261c1ed008288e17499250b11e80aa.camel@gmail.com> (raw)
In-Reply-To: <87e0dac344d927ca6e2655ce7f7433ff73da6b58.camel@gmail.com>

On Tue, 2024-07-02 at 20:28 +0100, Vitor Soares wrote:
> On Mon, 2024-07-01 at 23:59 +0000, Peng Fan wrote:
> > > Subject: [PATCH v1] arm64: dts: imx8mp: Fix VPU PGC power-domain
> > > parents
> > > 
> > > From: Vitor Soares <vitor.soares@toradex.com>
> > > 
> > > On iMX8M Plus QuadLite (VPU-less SoC), the dependency between
> > > VPU power domains lead to a deferred probe error during boot:
> > > [   17.140195] imx-pgc imx-pgc-domain.8: failed to command PGC
> > > [   17.147183] platform imx-pgc-domain.11: deferred probe pending:
> > > (reason unknown)
> > > [   17.147200] platform imx-pgc-domain.12: deferred probe pending:
> > > (reason unknown)
> > > [   17.147207] platform imx-pgc-domain.13: deferred probe pending:
> > > (reason unknown)
> > > 
> > > This is incorrect and should be the VPU blk-ctrl controlling these power
> > > domains, which is already doing it.
> > > 
> > > After removing the `power-domain` property from the VPU PGC nodes,
> > > both iMX8M Plus w/ and w/out VPU boot correctly. However, it breaks
> > > the suspend/resume functionality. A fix for this is pending, see Links.
> > > 
> > > Cc: <stable@vger.kernel.org>
> > > Fixes: df680992dd62 ("arm64: dts: imx8mp: add vpu pgc nodes")
> > > Link:
> > > Suggested-by: Lucas Stach <l.stach@pengutronix.de>
> > > Signed-off-by: Vitor Soares <vitor.soares@toradex.com>
> > 
> > For VPU-Less 8MP, all the VPU PGC nodes should be dropped,
> > right?
> 
> They don't need to be dropped. Taking the iMX8MM Lite variante as example (it
> also doesn't have VPU), the nodes are there and this issue is not present.
> 
> > 
> > Why not use bootloader to update the device tree based on fuse
> > settings?
> 
> While fixing VPU blk-ctrl suspend/resume functionality, I received feedback
> that
> this VPU GPC dependency is incorrect and is up to VPU blk-ctrl to control the
> GPC domains.

You find it here:
https://lore.kernel.org/all/fcd6acc268b8642371cf289149b2b1c3e90c7f45.camel@pengutronix.de/


Regards,
Vitor Soares
> As we disable the VPU blk-ctrl node on the bootloader, removing the dependency
> solves the issue.
> 
> Regards,
> Vitor Soares
> > 
> > Regards,
> > Peng.
> > 
> > > ---
> > >  arch/arm64/boot/dts/freescale/imx8mp.dtsi | 3 ---
> > >  1 file changed, 3 deletions(-)
> > > 
> > > diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> > > b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> > > index b92abb5a5c53..12548336b736 100644
> > > --- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> > > +++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
> > > @@ -882,21 +882,18 @@ pgc_vpumix: power-domain@19 {
> > > 
> > >                                         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>;
> > >                                         };
> > > --
> > > 2.34.1
> > 
> 


      reply	other threads:[~2024-07-02 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 12:43 [PATCH v1] arm64: dts: imx8mp: Fix VPU PGC power-domain parents Vitor Soares
2024-07-01 23:59 ` Peng Fan
2024-07-02 19:28   ` Vitor Soares
2024-07-02 20:32     ` Vitor Soares [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=4b2da701dd261c1ed008288e17499250b11e80aa.camel@gmail.com \
    --to=ivitro@gmail.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=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=vitor.soares@toradex.com \
    /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).