From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: Re: [PATCH v2 3/3] drm: rcar-du: Repair vblank for DRM page flips using the VSP
Date: Thu, 20 Jul 2017 11:22:34 -0300 [thread overview]
Message-ID: <20170720112234.295a47eb@vento.lan> (raw)
In-Reply-To: <20170711222942.27735-4-laurent.pinchart+renesas@ideasonboard.com>
Em Wed, 12 Jul 2017 01:29:42 +0300
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> escreveu:
> From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
>
> The driver recently switched from handling page flip completion in the
> DU vertical blanking handler to the VSP frame end handler to fix a race
> condition. This unfortunately resulted in incorrect timestamps in the
> vertical blanking events sent to userspace as vertical blanking is now
> handled after sending the event.
>
> To fix this we must reverse the order of the two operations. The easiest
> way is to handle vertical blanking in the VSP frame end handler before
> sending the event. The VSP frame end interrupt occurs approximately 50µs
> earlier than the DU frame end interrupt, but this should not cause any
> undue harm.
>
> As we need to handle vertical blanking even when page flip completion is
> delayed, the VSP driver now needs to call the frame end completion
> callback unconditionally, with a new argument to report whether page
> flip has completed.
>
> With this new scheme the DU vertical blanking interrupt isn't needed
> anymore, so we can stop enabling it.
>
> Fixes: d503a43ac06a ("drm: rcar-du: Register a completion callback with VSP1")
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Acked-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Thanks,
Mauro
prev parent reply other threads:[~2017-07-20 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 22:29 [PATCH v2 0/2] drm: rcar-du: Repair vblank event handling Laurent Pinchart
2017-07-11 22:29 ` [PATCH v2 1/3] drm: rcar-du: Use the VBK interrupt for vblank events Laurent Pinchart
2017-07-11 22:29 ` Laurent Pinchart
2017-07-12 10:34 ` Kieran Bingham
2017-07-11 22:29 ` [PATCH v2 2/3] drm: rcar-du: Fix planes to CRTC assignment when using the VSP Laurent Pinchart
2017-07-11 22:29 ` Laurent Pinchart
2017-07-12 10:30 ` Kieran Bingham
2017-07-12 12:13 ` Laurent Pinchart
2017-07-11 22:29 ` [PATCH v2 3/3] drm: rcar-du: Repair vblank for DRM page flips " Laurent Pinchart
2017-07-11 22:29 ` Laurent Pinchart
2017-07-20 14:22 ` Mauro Carvalho Chehab [this message]
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=20170720112234.295a47eb@vento.lan \
--to=mchehab@s-opensource.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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.