From: Nishanth Menon <nm@ti.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Frank Binns <frank.binns@imgtec.com>,
Donald Robson <donald.robson@imgtec.com>,
Matt Coster <matt.coster@imgtec.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Sarah Walker <sarah.walker@imgtec.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
<dri-devel@lists.freedesktop.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/imagination: DRM_POWERVR should depend on ARCH_K3
Date: Fri, 1 Dec 2023 00:13:27 -0600 [thread overview]
Message-ID: <20231201061327.mfadiwejp5akmlal@properly> (raw)
In-Reply-To: <b9360c2044a1001b9a5bcb5914611711d040d4fe.1701196029.git.geert+renesas@glider.be>
On 19:29-20231128, Geert Uytterhoeven wrote:
> The Imagination Technologies PowerVR Series 6 GPU is currently only
> supported on Texas Instruments K3 AM62x SoCs. Hence add a dependency on
> ARCH_K3, to prevent asking the user about this driver when configuring a
> kernel without Texas Instruments K3 Multicore SoC support.
>
> Fixes: 4babef0708656c54 ("drm/imagination: Add skeleton PowerVR driver")
Minor nitpick here - 12 char sha.. otherwise:
Reviewed-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/gpu/drm/imagination/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/imagination/Kconfig b/drivers/gpu/drm/imagination/Kconfig
> index 3bfa2ac212dccb73..af492dbd9afd4ed9 100644
> --- a/drivers/gpu/drm/imagination/Kconfig
> +++ b/drivers/gpu/drm/imagination/Kconfig
> @@ -6,6 +6,7 @@ config DRM_POWERVR
> depends on ARM64
> depends on DRM
> depends on PM
> + depends on ARCH_K3 || COMPILE_TEST
> select DRM_EXEC
> select DRM_GEM_SHMEM_HELPER
> select DRM_SCHED
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-12-01 6:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 18:29 [PATCH] drm/imagination: DRM_POWERVR should depend on ARCH_K3 Geert Uytterhoeven
2023-11-28 19:03 ` Javier Martinez Canillas
2023-11-28 19:16 ` Geert Uytterhoeven
2023-11-28 19:26 ` Javier Martinez Canillas
2023-11-29 8:35 ` Maxime Ripard
2023-11-29 8:45 ` Javier Martinez Canillas
2023-11-29 8:58 ` Geert Uytterhoeven
2023-11-29 9:13 ` Javier Martinez Canillas
2023-11-29 10:03 ` Geert Uytterhoeven
2023-11-29 9:22 ` Maxime Ripard
2023-11-29 10:10 ` Geert Uytterhoeven
2023-11-29 10:49 ` Maxime Ripard
2023-11-29 11:08 ` Geert Uytterhoeven
2023-11-29 11:34 ` Maxime Ripard
2023-11-29 12:25 ` Geert Uytterhoeven
2023-12-01 6:13 ` Nishanth Menon [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=20231201061327.mfadiwejp5akmlal@properly \
--to=nm@ti.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=donald.robson@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.binns@imgtec.com \
--cc=geert+renesas@glider.be \
--cc=kristo@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=sarah.walker@imgtec.com \
--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