From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, linux-kernel@vger.kernel.org
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/simpledrm: Drop superfluous primary plane .atomic_check return logic
Date: Mon, 5 Sep 2022 13:06:05 +0200 [thread overview]
Message-ID: <3cb956d7-aac0-6a1a-6be1-098057e2fd03@redhat.com> (raw)
In-Reply-To: <43e3dead-6089-c342-5050-34d7325bcb24@suse.de>
Hello Thomas,
On 9/5/22 12:57, Thomas Zimmermann wrote:
> Hi Javier
>
> Am 31.08.22 um 13:12 schrieb Javier Martinez Canillas:
>> The simpledrm_primary_plane_helper_atomic_check() function is more complex
>> than needed. It first checks drm_atomic_helper_check_plane_state() returns
>> value to decide whether to return this or zero.
>>
>> But it could just return that function return value directly. It also does
>> a check if new_plane_state->visible isn't set, but returns zero regardless.
>>
>> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
>> ---
>>
>> drivers/gpu/drm/tiny/simpledrm.c | 15 ++++-----------
>> 1 file changed, 4 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/tiny/simpledrm.c b/drivers/gpu/drm/tiny/simpledrm.c
>> index a81f91814595..0be47f40247a 100644
>> --- a/drivers/gpu/drm/tiny/simpledrm.c
>> +++ b/drivers/gpu/drm/tiny/simpledrm.c
>> @@ -485,21 +485,14 @@ static int simpledrm_primary_plane_helper_atomic_check(struct drm_plane *plane,
>> struct drm_plane_state *new_plane_state = drm_atomic_get_new_plane_state(new_state, plane);
>> struct drm_crtc *new_crtc = new_plane_state->crtc;
>> struct drm_crtc_state *new_crtc_state = NULL;
>> - int ret;
>>
>> if (new_crtc)
>> new_crtc_state = drm_atomic_get_new_crtc_state(new_state, new_crtc);
>>
>> - ret = drm_atomic_helper_check_plane_state(new_plane_state, new_crtc_state,
>> - DRM_PLANE_NO_SCALING,
>> - DRM_PLANE_NO_SCALING,
>> - false, false);
>> - if (ret)
>> - return ret;
>> - else if (!new_plane_state->visible)
>> - return 0;
>> -
>> - return 0;
>> + return drm_atomic_helper_check_plane_state(new_plane_state, new_crtc_state,
>> + DRM_PLANE_NO_SCALING,
>> + DRM_PLANE_NO_SCALING,
>> + false, false);
>
> I'm undecided on this change. I know it's correct and more to the point.
> But the call's logic is non-intuitive: the call either returns an error
> or we have to test ->visible afterwards. So I wrote it explicitly.
>
Yes, but the check has no effect so I found it even less intuitive. Maybe
add a comment then if you wan to keep the current code?
> I saw that your change to ssd130x also uses the pattern. If we find more
> such drivers, we could implement the atomic check as a helper. I suggest
> drm_plane_helper_atomic_check_fixed() in drm_plane_helper.c
>
Sure. I can add a preparatory change in v2 that adds that helper and then
use it in the follow-up patch.
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2022-09-05 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 11:12 Javier Martinez Canillas
2022-09-05 10:57 ` Thomas Zimmermann
2022-09-05 11:06 ` Javier Martinez Canillas [this message]
2022-09-05 11:37 ` Thomas Zimmermann
2022-09-05 11:45 ` Javier Martinez Canillas
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=3cb956d7-aac0-6a1a-6be1-098057e2fd03@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.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®