From: Robert Beckett <bob.beckett@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Robert Beckett <bob.beckett@collabora.com>
Subject: [PATCH v4 0/2] handle vblank when disabling ctc with interrupt disabled
Date: Fri, 28 Jun 2019 13:05:30 +0100 [thread overview]
Message-ID: <cover.1561722822.git.bob.beckett@collabora.com> (raw)
Add warning when about to send stale vblank.
Revert change that stops vblank info being updated if interrupts already
disabled. This fixes a stale vblank timestamp issue seen on drm/imx.
Changes since v2:
Split up the patch in to smaller pieces.
Add warning when about to send bogus vblank event.
Update vblank to best guess info during drm_vblank_disable_and_save.
Changes since v3:
Update cover letter text to describe remaining actions.
Drop drm/imx patches as they have now been merged.
Replace vblank info estimation patch with a revert of the issue that
caused the need for estimation.
Robert Beckett (2):
drm/vblank: warn on sending stale event
Revert "drm/vblank: Do not update vblank count if interrupts are
already disabled."
drivers/gpu/drm/drm_vblank.c | 35 +++++++++++++++++++++++++----------
1 file changed, 25 insertions(+), 10 deletions(-)
--
2.18.0
next reply other threads:[~2019-06-28 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 12:05 Robert Beckett [this message]
2019-06-28 12:05 ` [PATCH v4 1/2] drm/vblank: warn on sending stale event Robert Beckett
2019-06-28 12:10 ` Robert Beckett
2019-06-28 12:05 ` [PATCH v4 2/2] Revert "drm/vblank: Do not update vblank count if interrupts are already disabled." Robert Beckett
2019-06-28 12:13 ` Ville Syrjälä
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=cover.1561722822.git.bob.beckett@collabora.com \
--to=bob.beckett@collabora.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=p.zabel@pengutronix.de \
--cc=sean@poorly.run \
/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
all inboxes | Powered by JetHome®