All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Emre Ucan <eucan@de.adit-jv.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] drm: rcar-du: track dma-buf fences
Date: Tue, 24 Apr 2018 00:47:29 +0300	[thread overview]
Message-ID: <1983372.7zdgnCuEbH@avalon> (raw)
In-Reply-To: <1522839837-24294-1-git-send-email-eucan@de.adit-jv.com>

Hi Emre,

Sorry for the late reply.

On Wednesday, 4 April 2018 14:03:57 EEST Emre Ucan wrote:
> We have to check dma-buf reservation objects
> of our framebuffers before we use them.
> Otherwise, another driver might be writing
> on the same buffer which we are using.
> This would cause visible tearing effects
> on display.
> 
> We can use existing atomic helper functions
> to solve this problem.

I've always found the 72 columns limit in commit messages to be quite 
limiting, especially for the subject line. Out of curiosity, is there any 
specific reason why you limit it further ?

> v2 changes:
> - Remove drm_atomic_helper_wait_for_fences()
>   call in rcar_du_kms.c. The commit_tail()
>   function in drm_atomic_helper.c, which calls
>   our atomic_commit_tail() implementation,
>   already calls it.
> - Remove proposed rcar_du_vsp_set_fence_for_plane()
>   function. Call drm_gem_fb_prepare_fb(), which
>   calls drm_atomic_set_fence_for_plane().
> 
> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com>
> ---
>  drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> b/drivers/gpu/drm/rcar-du/rcar_du_vsp.c index 2c260c3..fbad616 100644
> --- a/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> +++ b/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> @@ -18,6 +18,7 @@
>  #include <drm/drm_fb_cma_helper.h>
>  #include <drm/drm_gem_cma_helper.h>
>  #include <drm/drm_plane_helper.h>
> +#include <drm/drm_gem_framebuffer_helper.h>

Nitpicking, could you please keep the headers alphabetically sorted ? It helps 
locating duplicates quickly.

>  #include <linux/bitops.h>
>  #include <linux/dma-mapping.h>
> @@ -237,7 +238,7 @@ static int rcar_du_vsp_plane_prepare_fb(struct drm_plane
> *plane, }
>  	}
> 
> -	return 0;
> +	return drm_gem_fb_prepare_fb(plane, state);

If drm_gem_fb_prepare_fb() fails we need to clean up the operations performed 
earlier in this function. I think the following would be enough.

        ret = drm_gem_fb_prepare_fb(plane, state);
        if (ret)
                goto fail;

        return 0;

Could you please test this ?

>  fail:
>  	while (i--) {

-- 
Regards,

Laurent Pinchart



_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-04-23 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 11:03 [PATCH v2] drm: rcar-du: track dma-buf fences Emre Ucan
2018-04-23 21:47 ` Laurent Pinchart [this message]
2018-04-30  8:40   ` Ucan, Emre (ADITG/ESB)
2018-04-30 11:43     ` Laurent Pinchart
2018-04-30 12:25       ` Ucan, Emre (ADITG/ESB)

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=1983372.7zdgnCuEbH@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eucan@de.adit-jv.com \
    /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.