From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/simpledrm: Do not call drm_atomic_add_affected_planes()
Date: Tue, 11 Oct 2022 15:06:19 +0200 [thread overview]
Message-ID: <fc9a8b09-4b41-291e-d235-bb71eeb95f3c@suse.de> (raw)
In-Reply-To: <20221010170203.274949-2-javierm@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1993 bytes --]
Hi
Am 10.10.22 um 19:02 schrieb Javier Martinez Canillas:
> There's no need to add planes to the atomic state. Remove the call
> to drm_atomic_add_affected_planes() from simpledrm.
>
> On full modesets, the DRM helpers already add a CRTC's planes to the
> atomic state; see drm_atomic_helper_check_modeset(). There's no reason
> to call drm_atomic_add_affected_planes() unconditionally in the CRTC's
> atomic_check() in simpledrm. It's also too late, as the atomic_check()
> of the added planes will not be called before the commit.
>
> Suggested-by: Thomas Zimmermann <tzimmermann@suse.de>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
There's also drm_atomic_add_affected_planes() in mgag200. Since you're
at it, I'd appreciate a patch.
Best regards
Thomas
> ---
>
> drivers/gpu/drm/tiny/simpledrm.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/tiny/simpledrm.c b/drivers/gpu/drm/tiny/simpledrm.c
> index ecd49a8f3334..f03f17f62a56 100644
> --- a/drivers/gpu/drm/tiny/simpledrm.c
> +++ b/drivers/gpu/drm/tiny/simpledrm.c
> @@ -549,17 +549,11 @@ static int simpledrm_crtc_helper_atomic_check(struct drm_crtc *crtc,
> struct drm_atomic_state *new_state)
> {
> struct drm_crtc_state *new_crtc_state = drm_atomic_get_new_crtc_state(new_state, crtc);
> - int ret;
>
> if (!new_crtc_state->enable)
> - goto out;
> -
> - ret = drm_atomic_helper_check_crtc_primary_plane(new_crtc_state);
> - if (ret)
> - return ret;
> + return 0;
>
> -out:
> - return drm_atomic_add_affected_planes(new_state, crtc);
> + return drm_atomic_helper_check_crtc_primary_plane(new_crtc_state);
> }
>
> /*
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-10-11 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 17:02 [PATCH 0/3] Add a drm_crtc_helper_atomic_check() helper Javier Martinez Canillas
2022-10-10 17:02 ` [PATCH 1/3] drm/simpledrm: Do not call drm_atomic_add_affected_planes() Javier Martinez Canillas
2022-10-11 13:06 ` Thomas Zimmermann [this message]
2022-10-11 13:09 ` Javier Martinez Canillas
2022-10-10 17:02 ` [PATCH 2/3] drm/ssd130x: " Javier Martinez Canillas
2022-10-11 13:09 ` Thomas Zimmermann
2022-10-10 17:02 ` [PATCH 3/3] drm/crtc-helper: Add a drm_crtc_helper_atomic_check() helper Javier Martinez Canillas
2022-10-11 13:21 ` Thomas Zimmermann
2022-10-11 13:26 ` Javier Martinez Canillas
2022-10-11 15:01 ` Thomas Zimmermann
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=fc9a8b09-4b41-291e-d235-bb71eeb95f3c@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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®