All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Conor Dooley <conor+dt@kernel.org>,
	Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.li@nxp.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Peng Fan <peng.fan@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Rain Yang <jiyu.yang@oss.nxp.com>, Rob Herring <robh@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	devicetree@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH] arm64: dts: imx95: Use GPU_CGC as core clock for GPU
Date: Sat, 17 Jan 2026 13:35:09 +0800	[thread overview]
Message-ID: <aWsfjTMz04r07bEU@dragon> (raw)
In-Reply-To: <20251129143220.14834-1-marek.vasut@mailbox.org>

On Sat, Nov 29, 2025 at 03:31:30PM +0100, Marek Vasut wrote:
> The i.MX95 imx-sm introduced new GPU_CGC clock since imx-sm commit
> ca5e078833fa ("SM-128: Add clock management via CCM LPCG direct control")
> which are downstream clock of GPU clock. These new GPU_CGC clock
> gate the existing GPU clock. Currently, without clk_ignore_unused
> on kernel command line, those new GPU_CGC clock are unused and the
> kernel will disable them. This has no impact on i.MX95 A0/A1, but
> does prevent GPU register access from working at all on i.MX95 B0.
> The GPU_CGC clock are present on both i.MX95 A0/A1/B0, therefore
> update the DT such, that the GPU core clock are the GPU_CGC clock.
> When the panthor driver enables the GPU core clock, it enables both
> the GPU_CGC as well as its parent GPU clock.
> 
> Fixes: 67934f248e64 ("arm64: dts: imx95: Describe Mali G310 GPU")
> Signed-off-by: Marek Vasut <marek.vasut@mailbox.org>

Applied, thanks!

      parent reply	other threads:[~2026-01-17  5:35 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
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 [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=aWsfjTMz04r07bEU@dragon \
    --to=shawnguo@kernel.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=marek.vasut@mailbox.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.