Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Rain Yang <jiyu.yang@oss.nxp.com>
Cc: Frank.li@nxp.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org, festevam@gmail.com,
	imx@lists.linux.dev, kernel@pengutronix.de, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org, peng.fan@nxp.com,
	robh@kernel.org, s.hauer@pengutronix.de, shawnguo@kernel.org
Subject: Re: [PATCH] arm64: dts: imx95: Use GPU_CGC as core clock for GPU
Date: Wed, 3 Dec 2025 23:48:47 +0100	[thread overview]
Message-ID: <de36091e-c890-4897-b3e3-2a7575029a5d@mailbox.org> (raw)
In-Reply-To: <aTACuRjC_Zpf8IOU@oss.nxp.com>

On 12/3/25 10:28 AM, Rain Yang wrote:

Hello Rain,

>>> Thanks for integrating this downstream patch.
>>
>> Which downstream patch do you refer to ?
>>
>>> Please note that CLK_GPUAPB and CLK_GPU are
>>> always-on, so the commit message should be amended accordingly.
>>
>> The GPU clock do not seem to be always-on, neither do the GPUAPB . It seems
>> the SM can turn those clock off perfectly well.
>>
>>> Additionally, the IMX95_CLK_GPUAPB handle shall be removed, as there is no valid OPP entry
>>> in the frequency table, this also helps minimize differences between downstream and upstream,
>>> reducing maintenance effort.
>>
>> Downstream kernel forks are not relevant to this discussion, upstream your
>> content and then you won't have to spend maintenance effort on downstream
>> stuff.
> 
> This patch [1] was the reference point.

Sigh ... I was not aware of that one.

Maybe next time, it would be good to upstream these changes directly ?

> For the Linux working environment,
> CLK_GPU and CLK_GPUAPB are always-on, while CLK_GPU_CGC can be gated off.
> 
> Regarding the IMX95_CLK_GPUAPB handle, my suggestion was based on the absence
> of its frequency in any OPP entry within the frequency table. Removing it
> could simplify the OPP handling logic and reduce unnecessary complexity.

If the clock can be disabled by SM, Linux has to make sure they are NOT 
disabled, so they must be described in DT, right ?

> [1] https://github.com/nxp-imx/linux-imx/commit/695f2bdc57b869ca5189313e4b5fa7eb5a12f622


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2025-12-03 23:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-29 14:31 [PATCH] arm64: dts: imx95: Use GPU_CGC as core clock for GPU Marek Vasut
2025-12-03  2:48 ` Rain Yang
2025-12-03  3:38   ` Marek Vasut
2025-12-03  9:28     ` Rain Yang
2025-12-03 22:48       ` Marek Vasut [this message]
2025-12-04  3:01         ` Rain Yang
2025-12-04  3:25           ` Marek Vasut
2025-12-05  8:17             ` Rain Yang
2025-12-07  9:01               ` Marek Vasut
2025-12-08  2:02                 ` Rain Yang
2025-12-30  1:53                   ` Marek Vasut
2025-12-30  2:53                     ` Rain Yang
2025-12-30 14:17                       ` Marek Vasut
2025-12-31  3:06                         ` Rain Yang
2025-12-31 14:09                           ` Marek Vasut
2026-01-17  5:35 ` 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=de36091e-c890-4897-b3e3-2a7575029a5d@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --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@oss.nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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