From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guangliu Ding <guangliu.ding@nxp.com>, Liviu Dudau <liviu.dudau@arm.com>
Cc: "Daniel Baluta (OSS)" <daniel.baluta@oss.nxp.com>,
Daniel Almeida <daniel.almeida@collabora.com>,
Alice Ryhl <aliceryhl@google.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Steven Price <steven.price@arm.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <frank.li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jiyu Yang <jiyu.yang@nxp.com>
Subject: Re: [PATCH 1/2] dt-bindings: gpu: mali-valhall-csf: Document i.MX952 support
Date: Wed, 1 Apr 2026 18:07:23 +0200 [thread overview]
Message-ID: <562530e9-a607-4dae-9b43-786a3946f795@kernel.org> (raw)
In-Reply-To: <AM0PR04MB47075AF2C5863FC665285CA9F350A@AM0PR04MB4707.eurprd04.prod.outlook.com>
On 01/04/2026 13:27, Guangliu Ding wrote:
>>>>
>>>> We discuss only the lack of compatibility in terms of DT, how DT sees
>>>> compatible devices.
>>>>
>>>> And lack of driver code is clear indication that devices are
>>>> compatible in terms how DT understands it. Feel encouraged to bring
>>>> actual arguments in commit msgs in the future.
>>>>
>>>> Best regards,
>>>> Krzysztof
>>>
>>> So the best approach is only reserve "arm,mali-valhall-csf" for now,
>>> since currently there is no need for an additional compatible entry from a DT
>> compatibility perspective.
>>> We can introduce "nxp,imx952-mali" in future commits if hardware or
>>> driver differences actually require it, and include more detailed justification
>> in the commit message. Right?
>>
>> So does that mean you decided not to read writing bindings document?
>
> Actually, I followed the compatible string of gpu node in imx952.dtsi during
> code work since they share the same GPU IP.
> gpu: gpu@4d900000 {
> compatible = "nxp,imx95-mali", "arm,mali-valhall-csf"; >
>
> Is this line in writing bindings document that you want to mention about?
> Could you please share more suggestions about the patch optimization?
> DO add new compatibles in case there are new features or bugs.
Please read entire file. I feel like you avoid doing this and just ask
me to give you shortcut.
There is more than one point from that trivial writing bindings file
which applies here.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-01 16:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 10:12 [PATCH 0/2] Enable Mali G310 GPU support on i.MX952 board Guangliu Ding
2026-03-31 10:12 ` [PATCH 1/2] dt-bindings: gpu: mali-valhall-csf: Document i.MX952 support Guangliu Ding
2026-03-31 14:31 ` Liviu Dudau
2026-04-01 8:48 ` [EXT] " Guangliu Ding
2026-04-01 8:56 ` Krzysztof Kozlowski
2026-04-01 9:19 ` Daniel Baluta
2026-04-01 9:43 ` Guangliu Ding
2026-04-01 10:13 ` Liviu Dudau
2026-04-01 10:31 ` Guangliu Ding
2026-04-01 10:38 ` Krzysztof Kozlowski
2026-04-01 11:01 ` Guangliu Ding
2026-04-01 11:03 ` Krzysztof Kozlowski
2026-04-01 11:27 ` Guangliu Ding
2026-04-01 16:07 ` Krzysztof Kozlowski [this message]
2026-04-01 17:52 ` [EXT] " Guangliu Ding
2026-04-01 15:26 ` Liviu Dudau
2026-04-01 15:59 ` Guangliu Ding
2026-04-01 17:20 ` Liviu Dudau
2026-04-01 18:03 ` Guangliu Ding
2026-04-02 15:14 ` Liviu Dudau
2026-04-01 7:40 ` Krzysztof Kozlowski
2026-04-01 9:11 ` Guangliu Ding
2026-03-31 10:12 ` [PATCH 2/2] arm64: dts: imx952: Describe Mali G310 GPU Guangliu Ding
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=562530e9-a607-4dae-9b43-786a3946f795@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=boris.brezillon@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=daniel.baluta@oss.nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=guangliu.ding@nxp.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=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=simona@ffwll.ch \
--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