From: "Stéphane Marchesin" <marcheu-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: shirish.s-5C7GfCeVMHo@public.gmane.org
Cc: Alexander.Deucher-5C7GfCeVMHo@public.gmane.org,
harry.wentland-5C7GfCeVMHo@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amd/display: remove need of modeset flag for overlay planes
Date: Tue, 01 May 2018 19:23:57 +0000 [thread overview]
Message-ID: <CADMs+9a0R1dbWyfwK-rtcQ05oTJnUCYa51ZgRDQcUaDfj1znhg@mail.gmail.com> (raw)
In-Reply-To: <1524824823-24271-1-git-send-email-shirish.s-5C7GfCeVMHo@public.gmane.org>
On Fri, Apr 27, 2018 at 3:27 AM Shirish S <shirish.s@amd.com> wrote:
> This patch is in continuation to the
> "843e3c7 drm/amd/display: defer modeset check in dm_update_planes_state"
> where we started to eliminate the dependency on
> DRM_MODE_ATOMIC_ALLOW_MODESET to be set by the user space,
> which as such is not mandatory.
> After deferring, this patch eliminates the dependency on the flag
> for overlay planes.
> This has to be done in stages as its a pretty complex and requires
thorough
> testing before we free primary planes as well from dependency on modeset
> flag.
> Signed-off-by: Shirish S <shirish.s@amd.com>
> ---
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index 1a63c04..87b661d 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -4174,7 +4174,7 @@ static void amdgpu_dm_commit_planes(struct
drm_atomic_state *state,
> }
> spin_unlock_irqrestore(&crtc->dev->event_lock, flags);
> - if (!pflip_needed) {
> + if (!pflip_needed || plane->type ==
DRM_PLANE_TYPE_OVERLAY) {
> WARN_ON(!dm_new_plane_state->dc_state);
> plane_states_constructed[planes_count] =
dm_new_plane_state->dc_state;
> @@ -4884,7 +4884,8 @@ static int dm_update_planes_state(struct dc *dc,
> /* Remove any changed/removed planes */
> if (!enable) {
> - if (pflip_needed)
> + if (pflip_needed &&
> + plane && plane->type !=
DRM_PLANE_TYPE_OVERLAY)
nit: I don't think we need to check that plane is non-NULL
Stéphane
> continue;
> if (!old_plane_crtc)
> @@ -4931,7 +4932,8 @@ static int dm_update_planes_state(struct dc *dc,
> if (!dm_new_crtc_state->stream)
> continue;
> - if (pflip_needed)
> + if (pflip_needed &&
> + plane && plane->type !=
DRM_PLANE_TYPE_OVERLAY)
> continue;
> WARN_ON(dm_new_plane_state->dc_state);
> --
> 2.7.4
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-05-01 19:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 10:27 [PATCH] drm/amd/display: remove need of modeset flag for overlay planes Shirish S
[not found] ` <1524824823-24271-1-git-send-email-shirish.s-5C7GfCeVMHo@public.gmane.org>
2018-05-01 19:23 ` Stéphane Marchesin [this message]
[not found] ` <CADMs+9a0R1dbWyfwK-rtcQ05oTJnUCYa51ZgRDQcUaDfj1znhg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-05-02 2:54 ` S, Shirish
2018-05-02 13:51 ` Harry Wentland
[not found] ` <b94fe6bd-5d9b-9f61-42d8-c47df54d9346-5C7GfCeVMHo@public.gmane.org>
2018-05-03 8:00 ` S, Shirish
[not found] ` <42b267f5-93c2-1682-af94-0cb9fc42ebb8-5C7GfCeVMHo@public.gmane.org>
2018-05-03 18:11 ` Harry Wentland
[not found] ` <67135740-35e6-4090-8f07-a5247c09a4be-5C7GfCeVMHo@public.gmane.org>
2018-05-04 12:57 ` Andrey Grodzovsky
[not found] ` <b3d563a3-31a9-45d1-492d-4d2a1ce9d7bb-5C7GfCeVMHo@public.gmane.org>
2018-05-07 10:12 ` S, Shirish
2018-05-09 20:53 ` Harry Wentland
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=CADMs+9a0R1dbWyfwK-rtcQ05oTJnUCYa51ZgRDQcUaDfj1znhg@mail.gmail.com \
--to=marcheu-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=harry.wentland-5C7GfCeVMHo@public.gmane.org \
--cc=shirish.s-5C7GfCeVMHo@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.