devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Peng Fan <peng.fan@nxp.com>, "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: "Markus.Niebel@ew.tq-group.com" <Markus.Niebel@ew.tq-group.com>,
	"aford173@gmail.com" <aford173@gmail.com>,
	Aisheng Dong <aisheng.dong@nxp.com>,
	"alexander.stein@ew.tq-group.com"
	<alexander.stein@ew.tq-group.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
	"laurent.pinchart@ideasonboard.com" 
	<laurent.pinchart@ideasonboard.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"marex@denx.de" <marex@denx.de>,
	"paul.elder@ideasonboard.com" <paul.elder@ideasonboard.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"gerg@kernel.org" <gerg@kernel.org>
Subject: Re: [PATCH] arm64: dts: imx8mp: add vpu pgc nodes
Date: Mon, 27 Mar 2023 23:23:53 +1000	[thread overview]
Message-ID: <87e68e05-8512-17fc-584c-0022ddefb8f0@linux-m68k.org> (raw)
In-Reply-To: <DU0PR04MB94174D60EE38B56FEB6CD5BC888B9@DU0PR04MB9417.eurprd04.prod.outlook.com>

Hi Peng,

On 27/3/23 20:01, Peng Fan wrote:
>> Subject: Re: [PATCH] arm64: dts: imx8mp: add vpu pgc nodes
>>
>> On 22/8/22 14:45, Peng Fan wrote:
>>> Add i.MX8MP PGC nodes for vpu, which are used to supply power for VPU.
>>>
>>> Signed-off-by: Peng Fan <peng.fan@nxp.com>
>>> Signed-off-by: Shawn Guo <shawnguo@kernel.org>
>>> ---
>>>   arch/arm64/boot/dts/freescale/imx8mp.dtsi | 27
>>> +++++++++++++++++++++++
>>>   1 file changed, 27 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>> b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>> index 0b165f98a82c..34af983b0210 100644
>>> --- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>> +++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
>>> @@ -598,6 +598,33 @@ 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>;
>>> +                                       };
>>>                                  };
>>>                          };
>>>                  };
>>
>> This change causes new error messages to come out during boot, for
>> example:
>>
>>      ...
>>      imx-pgc imx-pgc-domain.8: failed to command PGC
>>      imx-pgc imx-pgc-domain.8: failed to command PGC
>>      imx-pgc imx-pgc-domain.8: failed to command PGC
>>      30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 197, base_baud =
>> 1500000) is a IMX
>>      ...
>>      hwmon hwmon1: temp1_input not attached to any thermal zone
>>      imx-pgc imx-pgc-domain.8: failed to command PGC
>>      imx-pgc imx-pgc-domain.8: failed to command PGC
>>      imx-pgc imx-pgc-domain.8: failed to command PGC
>>      ...
>>
>> They don't seem to cause any problems on the hardware I am using, well, at
>> least not that I have found so far.
>>
>> This first appeared for me in linux-6.1. But it is the same in todays linux 6.3-
>> rc4. Reverting this change (not completely trivial due to a couple of commits
>> after it that rely on it) fixes it - no more errors.
> [Peng Fan]
> 
> The VPU BLK CTRL seems not enabled.

How to enable it?
I have the blk-ctrl config options enabled:

     #
     # i.MX SoC drivers
     #
     CONFIG_IMX_GPCV2_PM_DOMAINS=y
     CONFIG_SOC_IMX8M=y
     CONFIG_SOC_IMX9=y
     CONFIG_IMX8M_BLK_CTRL=y
     CONFIG_IMX9_BLK_CTRL=y
     # end of i.MX SoC drivers

Running with the full arm64 defconfig and using the imx8mp-evk.dtb still
outputs these messages:

     [   18.150679] imx-pgc imx-pgc-domain.8: failed to command PGC
     [   18.159241] imx-pgc imx-pgc-domain.8: failed to command PGC
     [   18.167822] imx-pgc imx-pgc-domain.8: failed to command PGC

Or do you mean something more fundamental, like the hardware block not
being enabled by boot loader?  (Something to keep in mind is that the
platform I am using has no video output, only serial console).

Regards
Greg


  reply	other threads:[~2023-03-27 13:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  6:36 [PATCH V2 0/6] imx: add i.MX8MP hdmi blk ctrl hdcp/hrv and vpu blk ctrl Peng Fan (OSS)
2022-07-13  6:36 ` [PATCH V2 1/6] dt-bindings: power: imx8mp-power: add HDMI HDCP/HRV Peng Fan (OSS)
2022-07-13  6:36 ` [PATCH V2 2/6] dt-bindings: soc: imx: add i.MX8MP vpu blk ctrl Peng Fan (OSS)
2022-07-13  8:29   ` Krzysztof Kozlowski
2022-07-13  9:03     ` Peng Fan
2022-07-13  9:11       ` Krzysztof Kozlowski
2022-07-13  9:15         ` Peng Fan
2022-07-13  6:36 ` [PATCH V2 3/6] soc: imx: add i.MX8MP HDMI blk ctrl HDCP/HRV Peng Fan (OSS)
2022-07-13  6:36 ` [PATCH V2 4/6] soc: imx: imx8m-blk-ctrl: add i.MX8MP VPU blk ctrl Peng Fan (OSS)
2022-07-13  6:36 ` [PATCH V2 5/6] arm64: dts: imx8mp: add vpu pgc nodes Peng Fan (OSS)
2023-03-27  5:06   ` [PATCH] " Greg Ungerer
2023-03-27 10:01     ` Peng Fan
2023-03-27 13:23       ` Greg Ungerer [this message]
2023-03-28  2:15         ` Peng Fan
2023-03-28  2:34           ` Greg Ungerer
2022-07-13  6:36 ` [PATCH V2 6/6] arm64: dts: imx8mp: add VPU blk ctrl node Peng Fan (OSS)
2022-07-16  7:50   ` kernel test robot

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=87e68e05-8512-17fc-584c-0022ddefb8f0@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=Markus.Niebel@ew.tq-group.com \
    --cc=aford173@gmail.com \
    --cc=aisheng.dong@nxp.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=gerg@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=paul.elder@ideasonboard.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@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).