From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matt Coster <matt.coster@imgtec.com>,
Frank Binns <frank.binns@imgtec.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>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Randolph Sapp <rs@ti.com>,
Darren Etheridge <detheridge@ti.com>
Subject: Re: [PATCH v2 05/21] drm/imagination: Use more specific compatible strings
Date: Wed, 20 Nov 2024 09:30:00 +0100 [thread overview]
Message-ID: <ea0bc7ea-eaf7-492a-b412-dc86baba23ff@kernel.org> (raw)
In-Reply-To: <20241118-sets-bxs-4-64-patch-v1-v2-5-3fd45d9fb0cf@imgtec.com>
On 18/11/2024 14:01, Matt Coster wrote:
> Follow-on from the companion dt-bindings change ("dt-bindings: gpu: img:
> More explicit compatible strings"), deprecating "img,img-axe" in favour of
> the more specific "img,img-axe-1-16m".
>
> Keep the previous compatible string around for backwards compatibility.
>
> Signed-off-by: Matt Coster <matt.coster@imgtec.com>
> ---
> Changes in v2:
> - None
> - Link to v1: https://lore.kernel.org/r/20241105-sets-bxs-4-64-patch-v1-v1-5-4ed30e865892@imgtec.com
> ---
> drivers/gpu/drm/imagination/pvr_drv.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/gpu/drm/imagination/pvr_drv.c b/drivers/gpu/drm/imagination/pvr_drv.c
> index 684a9b9a2247b8f5b0f4a91ec984af2cff5a4c29..fbd8802abcf1271e260209957d95ea705dbe7f14 100644
> --- a/drivers/gpu/drm/imagination/pvr_drv.c
> +++ b/drivers/gpu/drm/imagination/pvr_drv.c
> @@ -1471,6 +1471,16 @@ static void pvr_remove(struct platform_device *plat_dev)
> }
>
> static const struct of_device_id dt_match[] = {
> + { .compatible = "img,img-rogue", .data = NULL },
> +
> + /* All supported GPU models */
> + { .compatible = "img,img-axe-1-16m", .data = NULL },
This makes no sense. It's the same as rogue. Use compatibility properly.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-20 8:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 13:01 [PATCH v2 00/21] Imagination BXS-4-64 MC1 GPU support Matt Coster
2024-11-18 13:01 ` [PATCH v2 01/21] dt-bindings: gpu: img: More explicit compatible strings Matt Coster
2024-11-20 8:22 ` Krzysztof Kozlowski
2024-11-18 13:01 ` [PATCH v2 02/21] dt-bindings: gpu: img: Further constrain clocks Matt Coster
2024-11-20 8:25 ` Krzysztof Kozlowski
2024-11-25 18:02 ` Parthiban
2024-11-18 13:01 ` [PATCH v2 03/21] dt-bindings: gpu: img: Power domain details Matt Coster
2024-11-20 8:27 ` Krzysztof Kozlowski
2024-11-18 13:01 ` [PATCH v2 04/21] dt-bindings: gpu: img: Allow dma-coherent Matt Coster
2024-11-20 8:27 ` Krzysztof Kozlowski
2024-11-18 13:01 ` [PATCH v2 05/21] drm/imagination: Use more specific compatible strings Matt Coster
2024-11-20 8:30 ` Krzysztof Kozlowski [this message]
2024-11-18 13:01 ` [PATCH v2 06/21] drm/imagination: Add power domain control Matt Coster
2024-11-18 13:01 ` [PATCH v2 07/21] arm64: dts: ti: k3-am62: New GPU binding details Matt Coster
2024-11-20 8:32 ` Krzysztof Kozlowski
2024-11-18 13:02 ` [PATCH v2 08/21] dt-bindings: gpu: img: Add BXS-4-64 devicetree bindings Matt Coster
2024-11-20 8:28 ` Krzysztof Kozlowski
2024-11-18 13:02 ` [PATCH v2 09/21] drm/imagination: Revert to non-threaded IRQs Matt Coster
2024-11-18 13:02 ` [PATCH v2 10/21] drm/imagination: Remove firmware enable_reg Matt Coster
2024-11-18 13:02 ` [PATCH v2 11/21] drm/imagination: Rename event_mask -> status_mask Matt Coster
2024-11-18 13:02 ` [PATCH v2 12/21] drm/imagination: Make has_fixed_data_addr a value Matt Coster
2024-11-18 13:02 ` [PATCH v2 13/21] drm/imagination: Use a lookup table for fw defs Matt Coster
2024-11-18 13:02 ` [PATCH v2 14/21] drm/imagination: Use callbacks for fw irq handling Matt Coster
2024-11-18 13:02 ` [PATCH v2 15/21] drm/imagination: Add register required for RISC-V firmware Matt Coster
2024-11-18 13:02 ` [PATCH v2 16/21] drm/imagination: Move ELF fw utils to common file Matt Coster
2024-11-18 13:02 ` [PATCH v2 17/21] drm/imagination: Add RISC-V firmware processor support Matt Coster
2024-11-18 13:02 ` [PATCH v2 18/21] drm/imagination: Add platform overrides infrastructure Matt Coster
2024-11-18 13:02 ` [PATCH v2 19/21] drm/imagination: Add device_memory_force_cpu_cached override Matt Coster
2024-11-19 18:43 ` Andrew Davis
2024-11-18 13:02 ` [PATCH v2 20/21] drm/imagination: Add support for TI AM68 GPU Matt Coster
2024-11-18 13:02 ` [PATCH v2 21/21] arm64: dts: ti: k3-j721s2: Add GPU node Matt Coster
2024-11-20 8:33 ` Krzysztof Kozlowski
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=ea0bc7ea-eaf7-492a-b412-dc86baba23ff@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.binns@imgtec.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matt.coster@imgtec.com \
--cc=mripard@kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=rs@ti.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vigneshr@ti.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).