LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Helen Koike <helen.koike@collabora.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
nicholas.kazlauskas@amd.com, "Grodzovsky,
Andrey" <andrey.grodzovsky@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Tomasz Figa" <tfiga@chromium.org>,
boris.brezillon@collabora.com, "David Airlie" <airlied@linux.ie>,
"Sean Paul" <seanpaul@google.com>,
kernel@collabora.com, "Harry Wentland" <harry.wentland@amd.com>,
"Stéphane Marchesin" <marcheu@google.com>,
stable <stable@vger.kernel.org>, "Sean Paul" <sean@poorly.run>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
freedreno <freedreno@lists.freedesktop.org>,
"Mamta Shukla" <mamtashukla555@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>
Subject: Re: [PATCH v3 3/5] drm/msm: fix fb references in async update
Date: Wed, 27 Mar 2019 10:52:09 -0400 [thread overview]
Message-ID: <CAF6AEGtsZ7eoErhnq08kKv3d0NTEG-GKH52ucgvRPNOHkPcOjA@mail.gmail.com> (raw)
In-Reply-To: <20190314002027.7833-4-helen.koike@collabora.com>
On Wed, Mar 13, 2019 at 8:21 PM Helen Koike <helen.koike@collabora.com> wrote:
>
> Async update callbacks are expected to set the old_fb in the new_state
> so prepare/cleanup framebuffers are balanced.
>
> Cc: <stable@vger.kernel.org> # v4.14+
> Fixes: 224a4c970987 ("drm/msm: update cursors asynchronously through atomic")
> Suggested-by: Boris Brezillon <boris.brezillon@collabora.com>
> Signed-off-by: Helen Koike <helen.koike@collabora.com>
>
> ---
> Hello,
>
> As mentioned in the cover letter,
> But I couldn't test on MSM because I don't have the hardware and I would
> appreciate if anyone could test it.
>
> In other platforms (VC4, AMD, Rockchip), there is a hidden
> drm_framebuffer_get(new_fb)/drm_framebuffer_put(old_fb) in async_update
> that is wrong, but I couldn't identify those here, not sure if it is hidden
> somewhere else, but if tests fail this is probably the cause.
>
> Thanks!
> Helen
Apologies, I haven't had a chance to test this yet, and it is likely
to be a few weeks before I have a chance..
That said, not refcnt'ing the fb seems suspicious. I read the
explanation in the other patches, but kind of think it is more clear
to keep the extra refcnt'ing.. or at least have a comment.
I do a bit wonder if we hold the ref to the outgoing cursor long
enough.. I think the hw will actually continue to scan it out until
the next vblank. But Archit was the one who added async_update
support so maybe that is handled somewhere else. It's been a while
since I've looked at this.
BR,
-R
>
> Changes in v3: None
> Changes in v2:
> - update CC stable and Fixes tag
>
> drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c b/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c
> index be13140967b4..b854f471e9e5 100644
> --- a/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c
> +++ b/drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c
> @@ -502,6 +502,8 @@ static int mdp5_plane_atomic_async_check(struct drm_plane *plane,
> static void mdp5_plane_atomic_async_update(struct drm_plane *plane,
> struct drm_plane_state *new_state)
> {
> + struct drm_framebuffer *old_fb = plane->state->fb;
> +
> plane->state->src_x = new_state->src_x;
> plane->state->src_y = new_state->src_y;
> plane->state->crtc_x = new_state->crtc_x;
> @@ -524,6 +526,8 @@ static void mdp5_plane_atomic_async_update(struct drm_plane *plane,
>
> *to_mdp5_plane_state(plane->state) =
> *to_mdp5_plane_state(new_state);
> +
> + new_state->fb = old_fb;
> }
>
> static const struct drm_plane_helper_funcs mdp5_plane_helper_funcs = {
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-03-27 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 0:20 [PATCH v3 0/5] drm: Fix fb changes for async updates Helen Koike
2019-03-14 0:20 ` [PATCH v3 1/5] drm/rockchip: fix fb references in async update Helen Koike
2019-03-14 0:20 ` [PATCH v3 2/5] drm/amd: " Helen Koike
2019-03-14 0:20 ` [PATCH v3 3/5] drm/msm: " Helen Koike
2019-03-27 14:52 ` Rob Clark [this message]
2019-04-03 18:03 ` Helen Koike
2019-05-31 17:54 ` Helen Koike
2019-05-31 18:50 ` Rob Clark
2019-03-14 0:20 ` [PATCH v3 4/5] drm/vc4: " Helen Koike
2019-03-14 0:20 ` [PATCH v3 5/5] drm: don't block fb changes for async plane updates Helen Koike
2019-05-07 20:18 ` Sean Paul
2019-06-03 16:53 ` Helen Koike
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=CAF6AEGtsZ7eoErhnq08kKv3d0NTEG-GKH52ucgvRPNOHkPcOjA@mail.gmail.com \
--to=robdclark@gmail.com \
--cc=airlied@linux.ie \
--cc=andrey.grodzovsky@amd.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mamtashukla555@gmail.com \
--cc=marcheu@google.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=sean@poorly.run \
--cc=seanpaul@google.com \
--cc=stable@vger.kernel.org \
--cc=tfiga@chromium.org \
--cc=ville.syrjala@linux.intel.com \
--subject='Re: [PATCH v3 3/5] drm/msm: fix fb references in async update' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).