From: Shawn Guo <shawnguo2@yeah.net>
To: Rain Yang <jiyu.yang@oss.nxp.com>
Cc: airlied@gmail.com, boris.brezillon@collabora.com,
conor+dt@kernel.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, festevam@gmail.com,
imx@lists.linux.dev, kernel@pengutronix.de, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, liviu.dudau@arm.com,
maarten.lankhorst@linux.intel.com, marek.vasut@mailbox.org,
mripard@kernel.org, p.zabel@pengutronix.de, robh@kernel.org,
s.hauer@pengutronix.de, shawnguo@kernel.org, simona@ffwll.ch,
sre@kernel.org, steven.price@arm.com, tzimmermann@suse.de,
xianzhong.li@nxp.com
Subject: Re: [PATCH v3 2/2] arm64: dts: imx95: Describe Mali G310 GPU
Date: Tue, 28 Oct 2025 17:08:17 +0800 [thread overview]
Message-ID: <aQCIAfyUC6N5y2fB@dragon> (raw)
In-Reply-To: <aQB88c_AEC1RAZtH@oss.nxp.com>
On Tue, Oct 28, 2025 at 04:21:05PM +0800, Rain Yang wrote:
> On Mon, Oct 27, 2025 at 08:57:08AM +0800, Shawn Guo wrote:
> >On Sat, Oct 11, 2025 at 12:53:29PM +0200, Marek Vasut wrote:
> >> On 9/25/25 10:38 PM, Marek Vasut wrote:
> >> > The instance of the GPU populated in i.MX95 is the G310, describe this
> >> > GPU in the DT. Include dummy GPU voltage regulator and OPP tables.
> >> Is there still anything that should be changed with this patchset, or can it
> >> be applied ?
> >
> >I'm waiting binding change to be applied first. Or is it already done?
> >
> >Shawn
> >
> Hi Shawn,
> It might be better for Marek to remove the always-on GPUAPB clock from the DTS, given that
> it's an SCMI protocol clock and the kernel expects it to be available during operations.
>
> Also, the gpu_fix_reg appears unnecessary for the driver and could be removed[1].
>
> [1] https://cgit.freedesktop.org/drm/drm-misc/commit/?id=a8cb5ca53690aa809f4f65e14192753073e61a71,
> https://cgit.freedesktop.org/drm/drm-misc/commit/?id=02df3543f3e0ea572e2c739605ebd6c20e1149c4
Ah, sorry! I did not know we haven't reached agreement on the change.
Shawn
next prev parent reply other threads:[~2025-10-28 9:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 20:38 [PATCH v3 1/2] dt-bindings: gpu: mali-valhall-csf: Document i.MX95 support Marek Vasut
2025-09-25 20:38 ` [PATCH v3 2/2] arm64: dts: imx95: Describe Mali G310 GPU Marek Vasut
2025-09-25 21:34 ` Frank Li
2025-09-26 5:57 ` Peng Fan
2025-09-29 0:23 ` Marek Vasut
2025-09-29 9:57 ` Rain Yang
2025-09-29 13:09 ` Marek Vasut
2025-09-29 16:20 ` Rain Yang
2025-09-29 17:10 ` Marek Vasut
2025-10-11 10:53 ` Marek Vasut
2025-10-27 0:57 ` Shawn Guo
2025-10-28 8:21 ` Rain Yang
2025-10-28 9:08 ` Shawn Guo [this message]
2025-11-02 16:02 ` Marek Vasut
2025-11-03 7:46 ` Rain Yang
2025-11-03 23:47 ` 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=aQCIAfyUC6N5y2fB@dragon \
--to=shawnguo2@yeah.net \
--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=jiyu.yang@oss.nxp.com \
--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=marek.vasut@mailbox.org \
--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 \
--cc=xianzhong.li@nxp.com \
/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).