linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Rain Yang <jiyu.yang@oss.nxp.com>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: Frank.Li@nxp.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org, festevam@gmail.com,
	imx@lists.linux.dev, jiyu.yang@nxp.com, kernel@pengutronix.de,
	krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, liviu.dudau@arm.com,
	marek.vasut@mailbox.org, robh@kernel.org, s.hauer@pengutronix.de,
	shawnguo@kernel.org
Subject: Re: [PATCH] arm64: dts: imx95: remove CLK_GPUAPB
Date: Fri, 2 Jan 2026 18:37:54 +0800	[thread overview]
Message-ID: <aVegAt002L20oBGf@oss.nxp.com> (raw)
In-Reply-To: <b2dd2109-c2d9-412e-9b11-5851485acf04@mailbox.org>

On Thu, Jan 01, 2026 at 05:51:12PM +0100, Marek Vasut wrote:
>On 1/1/26 1:37 AM, Rain Yang wrote:
>> On Wed, Dec 31, 2025 at 03:11:21PM +0100, Marek Vasut wrote:
>> > On 12/31/25 4:19 AM, Rain Yang wrote:
>> > > From: Rain Yang <jiyu.yang@nxp.com>
>> > > 
>> > > Dropping CLK_GPUAPB simplifies OPP handling and avoids unnecessary
>> > > complexity.
>> > > 
>> > > Fixes: 67934f248e64 ("arm64: dts: imx95: Describe Mali G310 GPU")
>> > > Signed-off-by: Rain Yang <jiyu.yang@nxp.com>
>> > > ---
>> > >    arch/arm64/boot/dts/freescale/imx95.dtsi | 4 ++--
>> > >    1 file changed, 2 insertions(+), 2 deletions(-)
>> > > 
>> > > diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
>> > > index 88bde59e61b2..ab446aa6f73c 100644
>> > > --- a/arch/arm64/boot/dts/freescale/imx95.dtsi
>> > > +++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
>> > > @@ -2164,8 +2164,8 @@ netc_emdio: mdio@0,0 {
>> > >    		gpu: gpu@4d900000 {
>> > >    			compatible = "nxp,imx95-mali", "arm,mali-valhall-csf";
>> > >    			reg = <0 0x4d900000 0 0x480000>;
>> > > -			clocks = <&scmi_clk IMX95_CLK_GPU_CGC>, <&scmi_clk IMX95_CLK_GPUAPB>;
>> > > -			clock-names = "core", "coregroup";
>> > > +			clocks = <&scmi_clk IMX95_CLK_GPU_CGC>;
>> > > +			clock-names = "core";
>> > 
>> > I don't think this is correct, SM can disable the GPUAPB clock from the SM
>> > monitor:
>> > 
>> > > $ clock.w gpuapb off
>> > 
>> > Linux has to make sure the GPUAPB clock are enabled to access the GPU
>> > register, hence the clock have to be described in DT.
>> Hi Marek,
>
>Hello Jiyu,
>
>> CLK_GPU and CLK_GPUAPB can only be controlled internally by the SM, not by Linux.
>> CLK_GPUAPB always runs at a fixed frequency, does not require dynamic adjustment,
>> and is practically always on.
>> Additionally, CLK_GPUAPB's frequency is absent from all OPP entries. Removing it
>> could simplify OPP handling logic and reduce unnecessary complexity.
>
>But the SM can turn the GPUAPB clock off, correct ?
>
>Linux has to be able to turn GPUAPB clock on, therefore the GPUAPB clock have
>to be described in DT, correct ?

Yes, CLK_GPUAPB can be turned off by the SM, but by default it remains on, just like
CLK_GPU. AFAIK, there is no scenario where either of these clocks could or would be
disabled in both SM and Linux.

If enabling or disabling CLK_GPUAPB in Linux was wanted, the same shall apply to CLK_GPU
to make this approach reasonable.
Also, OPP framework shall be adjusted to meet these changes too.


  reply	other threads:[~2026-01-02 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31  3:19 [PATCH] arm64: dts: imx95: remove CLK_GPUAPB Rain Yang
2025-12-31 14:11 ` Marek Vasut
2026-01-01  0:37   ` Rain Yang
2026-01-01 16:51     ` Marek Vasut
2026-01-02 10:37       ` Rain Yang [this message]
2026-01-02 13:53         ` Marek Vasut

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=aVegAt002L20oBGf@oss.nxp.com \
    --to=jiyu.yang@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=jiyu.yang@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=marek.vasut@mailbox.org \
    --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).