From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, linux-kernel@vger.kernel.org
Cc: Maxime Ripard <mripard@kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/ssd130x: Allocate buffers in the plane's .atomic_check callback
Date: Thu, 27 Jul 2023 15:43:44 +0200 [thread overview]
Message-ID: <874jlp5v1r.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <76cea601-2730-21a7-f52b-1d53be343d6e@suse.de>
Thomas Zimmermann <tzimmermann@suse.de> writes:
Hello Thomas,
Thanks a lot for the feedback!
> Hi Javier,
>
> this patch is completely broken. It's easy to fix though.
>
> Am 21.07.23 um 09:09 schrieb Javier Martinez Canillas:
[...]
>> +struct ssd130x_plane_state {
>> + struct drm_plane_state base;
>
> You need to use a struct drm_shadow_plane_state here.
>
Yes, I already noticed this when testing Arnd's patch to drop
DRM_GEM_SHADOW_PLANE_FUNCS. I already have a patch ready.
[...]
+
>> static const struct drm_plane_helper_funcs ssd130x_primary_plane_helper_funcs = {
>> DRM_GEM_SHADOW_PLANE_HELPER_FUNCS,
>
> This macro sets the callbacks that vmap/vunmap the GEM buffer during the
> display update. They expect to upcast from drm_plane_state to
> drm_shadow_plane_state. And hence, your driver's plane state needs to
> inherit from drm_shadow_plane_state.
>
Yup. I missed that. I'm now testing my patch and will post it.
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
prev parent reply other threads:[~2023-07-27 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 7:09 Javier Martinez Canillas
2023-07-21 7:33 ` Maxime Ripard
2023-07-25 19:21 ` Geert Uytterhoeven
2023-07-25 20:49 ` Javier Martinez Canillas
2023-07-26 9:59 ` Maxime Ripard
2023-07-26 10:39 ` Javier Martinez Canillas
2023-07-26 11:52 ` Geert Uytterhoeven
2023-07-26 12:22 ` Javier Martinez Canillas
2023-07-26 12:33 ` Geert Uytterhoeven
2023-07-26 13:54 ` Maxime Ripard
2023-07-26 14:14 ` Geert Uytterhoeven
2023-07-26 14:22 ` Javier Martinez Canillas
2023-07-26 13:49 ` Maxime Ripard
2023-07-26 14:16 ` Javier Martinez Canillas
2023-07-27 12:52 ` Thomas Zimmermann
2023-07-27 13:43 ` Javier Martinez Canillas [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=874jlp5v1r.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--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
all inboxes | Powered by JetHome®