From: Steven Price <steven.price@arm.com>
To: carsten.haitzler@foss.arm.com, dri-devel@lists.freedesktop.org
Cc: liviu.dudau@arm.com, brian.starkey@arm.com, airlied@linux.ie,
daniel@ffwll.ch, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/arm: arm hdlcd select DRM_GEM_CMA_HELPER
Date: Mon, 24 Jan 2022 16:13:46 +0000 [thread overview]
Message-ID: <b302b8f4-40de-7b88-fbf5-933707476cdb@arm.com> (raw)
In-Reply-To: <20220124151357.2467149-1-carsten.haitzler@foss.arm.com>
On 24/01/2022 15:13, carsten.haitzler@foss.arm.com wrote:
> From: Carsten Haitzler <carsten.haitzler@arm.com>
>
> Without DRM_GEM_CMA_HELPER HDLCD won't build. This needs to be there too.
>
> Signed-off-by: Carsten Haitzler <carsten.haitzler@arm.com>
To add the context, DRM_HDLCD used to select DRM_KMS_CMA_HELPER but that
was removed in commit 09717af7d13d ("drm: Remove
CONFIG_DRM_KMS_CMA_HELPER option"). DRM_KMS_CMA_HELPER would select
DRM_GEM_CMA_HELPER but that transitive dependency was lost and
apparently the fixup was missed in that commit.
So we need a:
Fixes: 09717af7d13d ("drm: Remove CONFIG_DRM_KMS_CMA_HELPER option")
and with that...
Reviewed-by: Steven Price <steven.price@arm.com>
Steve
> ---
> drivers/gpu/drm/arm/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/arm/Kconfig b/drivers/gpu/drm/arm/Kconfig
> index 58a242871b28..6e3f1d600541 100644
> --- a/drivers/gpu/drm/arm/Kconfig
> +++ b/drivers/gpu/drm/arm/Kconfig
> @@ -6,6 +6,7 @@ config DRM_HDLCD
> depends on DRM && OF && (ARM || ARM64 || COMPILE_TEST)
> depends on COMMON_CLK
> select DRM_KMS_HELPER
> + select DRM_GEM_CMA_HELPER
> help
> Choose this option if you have an ARM High Definition Colour LCD
> controller.
>
next prev parent reply other threads:[~2022-01-24 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 15:13 carsten.haitzler
2022-01-24 16:13 ` Steven Price [this message]
2022-01-24 16:25 ` Carsten Haitzler
2022-01-24 16:24 carsten.haitzler
2022-01-25 12:37 ` Liviu Dudau
2022-02-23 10:18 ` Andre Przywara
2022-02-28 19:36 ` Rob Herring
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=b302b8f4-40de-7b88-fbf5-933707476cdb@arm.com \
--to=steven.price@arm.com \
--cc=airlied@linux.ie \
--cc=brian.starkey@arm.com \
--cc=carsten.haitzler@foss.arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.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
all inboxes | Powered by JetHome®