From: Lucas Stach <l.stach@pengutronix.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Sascha Hauer <kernel@pengutronix.de>,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH 5/5] drm/imx: add exclusive fence to plane state
Date: Tue, 20 Sep 2016 09:02:42 +0200 [thread overview]
Message-ID: <1474354962.5978.3.camel@pengutronix.de> (raw)
In-Reply-To: <CAKMK7uHYB=jL47f+c=CUMMDjmH8iW_SBo6XA_P23+-P3K=zokA@mail.gmail.com>
Am Montag, den 19.09.2016, 22:48 +0200 schrieb Daniel Vetter:
> On Thu, Aug 11, 2016 at 11:18 AM, Lucas Stach <l.stach@pengutronix.de> wrote:
> > This allows the atomic helper to wait on them, instead of open-coding
> > the same in the imx-drm driver.
> >
> > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > ---
> > drivers/gpu/drm/imx/imx-drm-core.c | 63 +++++++++++++++++---------------------
> > 1 file changed, 28 insertions(+), 35 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/imx/imx-drm-core.c b/drivers/gpu/drm/imx/imx-drm-core.c
> > index 66b3556f7b79..2d3f32f1b13b 100644
> > --- a/drivers/gpu/drm/imx/imx-drm-core.c
> > +++ b/drivers/gpu/drm/imx/imx-drm-core.c
> > @@ -152,50 +152,43 @@ static void imx_drm_output_poll_changed(struct drm_device *drm)
> > drm_fbdev_cma_hotplug_event(imxdrm->fbhelper);
> > }
> >
> > +static int imx_drm_atomic_commit(struct drm_device *dev,
> > + struct drm_atomic_state *state,
> > + bool nonblock)
> > +{
> > + struct drm_plane_state *plane_state;
> > + struct drm_plane *plane;
> > + struct dma_buf *dma_buf;
> > + int i;
> > +
> > + /*
> > + * If the plane fb has an dma-buf attached, fish out the exclusive
> > + * fence for the atomic helper to wait on.
> > + */
> > + for_each_plane_in_state(state, plane, plane_state, i) {
> > + if ((plane->state->fb != plane_state->fb) && plane_state->fb) {
> > + dma_buf = drm_fb_cma_get_gem_obj(plane_state->fb,
> > + 0)->base.dma_buf;
> > + if (!dma_buf)
> > + continue;
> > + plane_state->fence =
> > + reservation_object_get_excl_rcu(dma_buf->resv);
> > + }
> > + }
>
> Just an fyi, but the idea was that you could do this in youre
> prepare_plane hook, assuming that only when userspace flips is it
> interested in syncing (for backwards compat reasons). But this gets
> the job done too.
>
> The upshot of doing this consistently in a prepare_plane hook is that
> it would then allow us to have a shared implementation for all cma
> based kms drivers. If you feel bored, I'd be happy to take a look at a
> refactor patch which would extract that helper (and wire it up for
> imx).
>
Thanks for letting me know.
As our original flight to XDC has been canceled and we are re-routed to
the evening flight the boredom might actually kick in. :)
Regards,
Lucas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-20 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 9:18 [PATCH 1/5] drm/imx: don't call disable_plane in plane destroy path Lucas Stach
2016-08-11 9:18 ` [PATCH 2/5] drm/imx: drop deprecated load/unload drm_driver ops Lucas Stach
2016-08-11 9:18 ` [PATCH 3/5] drm/imx: don't destroy mode objects manually on driver unbind Lucas Stach
2016-08-11 9:18 ` [PATCH 4/5] drm/imx: fold ipu_plane_disable into ipu_disable_plane Lucas Stach
2016-08-11 9:18 ` [PATCH 5/5] drm/imx: add exclusive fence to plane state Lucas Stach
2016-09-19 20:48 ` Daniel Vetter
2016-09-20 7:02 ` Lucas Stach [this message]
2016-08-29 10:53 ` [PATCH 1/5] drm/imx: don't call disable_plane in plane destroy path Philipp Zabel
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=1474354962.5978.3.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=patchwork-lst@pengutronix.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;
as well as URLs for NNTP newsgroup(s).