From: Andre Przywara <andre.przywara@arm.com>
To: Liviu Dudau <liviu.dudau@arm.com>, carsten.haitzler@foss.arm.com
Cc: dri-devel@lists.freedesktop.org, brian.starkey@arm.com,
airlied@linux.ie, daniel@ffwll.ch, steven.price@arm.com,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] drm/arm: arm hdlcd select DRM_GEM_CMA_HELPER
Date: Wed, 23 Feb 2022 10:18:51 +0000 [thread overview]
Message-ID: <20220223101851.46423dcf@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <Ye/vEilz6j8gX3wu@e110455-lin.cambridge.arm.com>
On Tue, 25 Jan 2022 12:37:38 +0000
Liviu Dudau <liviu.dudau@arm.com> wrote:
Hi,
> On Mon, Jan 24, 2022 at 04:24:37PM +0000, 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.
> >
> > Fixes: 09717af7d13d ("drm: Remove CONFIG_DRM_KMS_CMA_HELPER option")
> >
> > Signed-off-by: Carsten Haitzler <carsten.haitzler@arm.com>
>
> Acked-by: Liviu Dudau <liviu.dudau@arm.com>
>
> I will add Steven's reviewed-by as well when pushing it.
Did this go anywhere? I see my .config just selecting HDLCD still failing
with -rc5. Any chance this can be taken now, as this is a regression
introduced with -rc1?
Cheers,
Andre
> > ---
> > 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.
> > --
> > 2.30.1
> >
>
next prev parent reply other threads:[~2022-02-23 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 16:24 carsten.haitzler
2022-01-25 12:37 ` Liviu Dudau
2022-02-23 10:18 ` Andre Przywara [this message]
2022-02-28 19:36 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2022-01-24 15:13 carsten.haitzler
2022-01-24 16:13 ` Steven Price
2022-01-24 16:25 ` Carsten Haitzler
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=20220223101851.46423dcf@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=brian.starkey@arm.com \
--cc=carsten.haitzler@foss.arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=steven.price@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®