linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Marek Vasut <marex@denx.de>, Frank Li <Frank.li@nxp.com>
Cc: linux-arm-kernel@lists.infradead.org,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Conor Dooley <conor+dt@kernel.org>,
	David Airlie <airlied@gmail.com>,
	Fabio Estevam <festevam@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Liviu Dudau <liviu.dudau@arm.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Rob Herring <robh@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Sebastian Reichel <sre@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>, Simona Vetter <simona@ffwll.ch>,
	Steven Price <steven.price@arm.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	imx@lists.linux.dev
Subject: Re: [PATCH 9/9] arm64: dts: imx95: Describe Mali G310 GPU
Date: Fri, 28 Feb 2025 11:39:18 +0100	[thread overview]
Message-ID: <3332618.oiGErgHkdL@steina-w> (raw)
In-Reply-To: <Z8DlYjq+87sjS9cU@lizhi-Precision-Tower-5810>

Am Donnerstag, 27. Februar 2025, 23:21:22 CET schrieb Frank Li:
> On Thu, Feb 27, 2025 at 10:34:20PM +0100, Marek Vasut wrote:
> > On 2/27/25 10:27 PM, Frank Li wrote:
> >
> > [...]
> >
> > > > > > +		gpu: gpu@4d900000 {
> > > > > > +			compatible = "fsl,imx95-mali", "arm,mali-valhall-csf";
> > > > > > +			reg = <0 0x4d900000 0 0x480000>;
> > > > > > +			clocks = <&scmi_clk IMX95_CLK_GPU>;
> > > > > > +			clock-names = "core";
> > > > > > +			interrupts = <GIC_SPI 288 IRQ_TYPE_LEVEL_HIGH>,
> > > > > > +				     <GIC_SPI 289 IRQ_TYPE_LEVEL_HIGH>,
> > > > > > +				     <GIC_SPI 290 IRQ_TYPE_LEVEL_HIGH>;
> > > > > > +			interrupt-names = "gpu", "job", "mmu";
> > > > > > +			mali-supply = <&gpu_fixed_reg>;
> > > > > > +			operating-points-v2 = <&gpu_opp_table>;
> > > > > > +			power-domains = <&scmi_devpd IMX95_PD_GPU>, <&scmi_perf IMX95_PERF_GPU>;
> > > > > > +			power-domain-names = "mix", "perf";
> > > > > > +			resets = <&gpu_blk_ctrl 0>;
> > > > > > +			#cooling-cells = <2>;
> > > > > > +			dynamic-power-coefficient = <1013>;
> > > > > > +			status = "disabled";
> > > > >
> > > > > GPU is internal module, which have not much dependence with other module
> > > > > such as pinmux. why not default status is "disabled". Supposed gpu driver
> > > > > will turn off clock and power if not used.
> > > > My thinking was that there are MX95 SoC with GPU fused off, hence it is
> > > > better to keep the GPU disabled in DT by default. But I can also keep it
> > > > enabled and the few boards which do not have MX95 SoC with GPU can
> > > > explicitly disable it in board DT.
> > > >
> > > > What do you think ?
> > >
> > > GPU Fuse off should use access-control, see thread
> > > https://lore.kernel.org/imx/20250207120213.GD14860@localhost.localdomain/
> > Did that thread ever go anywhere ? It seems there is no real conclusion, is
> > there ? +Cc Alex .
> 
> The direction is use access-control to indicate fuse disable. Only
> implement detail is under discussion.

Well, the discussion ended up to be more complicated for i.MX8M. For i.MX95
things are a bit easier, as fuses and clocks are controlled by System
Manager (SM), accessed using SCMI. [1] is more important for imx95.

Best regards
Alexander

[1] https://lore.kernel.org/all/20250204-imx-ocotp-v8-0-01be4a4bb045@nxp.com/
-- 
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/




  reply	other threads:[~2025-02-28 11:10 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 16:58 [PATCH 0/9] arm64: dts: imx95: Add support for Mali G310 GPU Marek Vasut
2025-02-27 16:58 ` [PATCH 1/9] dt-bindings: reset: imx95-gpu-blk-ctrl: Document Freescale i.MX95 GPU reset Marek Vasut
2025-02-27 17:30   ` Frank Li
2025-02-27 20:22     ` Marek Vasut
2025-02-27 18:38   ` Rob Herring (Arm)
2025-02-27 16:58 ` [PATCH 2/9] reset: simple: Add support for " Marek Vasut
2025-02-27 17:32   ` Frank Li
2025-02-28  9:58   ` Alexander Stein
2025-02-28 16:43     ` Marek Vasut
2025-02-27 16:58 ` [PATCH 3/9] dt-bindings: gpu: mali-valhall-csf: Document optional reset Marek Vasut
2025-02-27 17:33   ` Frank Li
2025-02-27 18:38   ` Rob Herring (Arm)
2025-02-28 12:25   ` Rob Herring (Arm)
2025-02-27 16:58 ` [PATCH 4/9] drm/panthor: Implement " Marek Vasut
2025-02-28 10:06   ` Alexander Stein
2025-02-28 16:48     ` Marek Vasut
2025-03-01 21:45   ` kernel test robot
2025-02-27 16:58 ` [PATCH 5/9] drm/panthor: Implement support for multiple power domains Marek Vasut
2025-02-28 10:10   ` Alexander Stein
2025-02-28 17:00     ` Marek Vasut
2025-02-27 16:58 ` [PATCH 6/9] drm/panthor: Reset GPU after L2 cache power off Marek Vasut
2025-02-27 17:17   ` Boris Brezillon
2025-02-27 17:26     ` Marek Vasut
2025-02-28 11:06   ` Liviu Dudau
2025-02-28 17:05     ` Marek Vasut
2025-03-03 12:08       ` Liviu Dudau
2025-03-03 12:35         ` Boris Brezillon
2025-03-03 12:42           ` Boris Brezillon
2025-03-21 20:00             ` Marek Vasut
2025-03-21 19:54           ` Marek Vasut
2025-02-27 16:58 ` [PATCH 7/9] dt-bindings: gpu: mali-valhall-csf: Document i.MX95 support Marek Vasut
2025-02-27 17:34   ` Frank Li
2025-02-27 18:38   ` Rob Herring (Arm)
2025-02-27 20:31     ` Marek Vasut
2025-02-28 12:28       ` Rob Herring
2025-02-28 10:12   ` Alexander Stein
2025-02-28 12:30   ` Rob Herring
2025-02-28 17:17     ` Marek Vasut
2025-02-27 16:58 ` [PATCH 8/9] drm/panthor: Add " Marek Vasut
2025-02-27 17:35   ` Frank Li
2025-02-27 20:17   ` Marco Felsch
2025-02-27 20:39     ` Marek Vasut
2025-02-28 10:33       ` Marco Felsch
2025-02-28 17:20         ` Marek Vasut
2025-02-28 10:21   ` Alexander Stein
2025-02-28 11:23     ` Florent Tomasin
2025-02-28 17:26       ` Marek Vasut
2025-03-03 13:55         ` Florent Tomasin
2025-02-28 17:21     ` Marek Vasut
2025-02-27 16:58 ` [PATCH 9/9] arm64: dts: imx95: Describe Mali G310 GPU Marek Vasut
2025-02-27 17:43   ` Frank Li
2025-02-27 20:36     ` Marek Vasut
2025-02-27 21:27       ` Frank Li
2025-02-27 21:34         ` Marek Vasut
2025-02-27 22:21           ` Frank Li
2025-02-28 10:39             ` Alexander Stein [this message]
2025-02-28 17:33               ` Marek Vasut
2025-02-28 10:36   ` Alexander Stein
2025-02-28 17:43     ` Marek Vasut
2025-03-03 15:04       ` Liviu Dudau
2025-03-21 19:37         ` Marek Vasut
2025-02-28 14:23 ` [PATCH 0/9] arm64: dts: imx95: Add support for " Rob Herring (Arm)

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=3332618.oiGErgHkdL@steina-w \
    --to=alexander.stein@ew.tq-group.com \
    --cc=Frank.li@nxp.com \
    --cc=airlied@gmail.com \
    --cc=boris.brezillon@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=liviu.dudau@arm.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marex@denx.de \
    --cc=mripard@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=sre@kernel.org \
    --cc=steven.price@arm.com \
    --cc=tzimmermann@suse.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 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).