From: Robert Beckett <bob.beckett@collabora•com>
To: dri-devel@lists•freedesktop.org
Cc: Robert Beckett <bob.beckett@collabora•com>,
Fabio Estevam <festevam@gmail•com>,
Daniel Vetter <daniel@ffwll•ch>,
Maxime Ripard <maxime.ripard@bootlin•com>,
Shawn Guo <shawnguo@kernel•org>,
Sascha Hauer <s.hauer@pengutronix•de>,
Maarten Lankhorst <maarten.lankhorst@linux•intel.com>,
linux-kernel@vger•kernel.org, David Airlie <airlied@linux•ie>,
NXP Linux Team <linux-imx@nxp•com>,
Philipp Zabel <p.zabel@pengutronix•de>,
Sean Paul <sean@poorly•run>,
Pengutronix Kernel Team <kernel@pengutronix•de>,
linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3 0/4] handle vblank when disabling ctc with interrupt disabled (was [PATCH v2] drm/imx: correct order of crtc disable)
Date: Tue, 25 Jun 2019 18:59:11 +0100 [thread overview]
Message-ID: <cover.1561483965.git.bob.beckett@collabora.com> (raw)
Handle vblank event sent to signal crtc disable while the backend vblank
interrupt has already been disabled by vblank_disable_fn.
Fixes: a474478642d5 ("drm/imx: fix crtc vblank state regression")
Fixes: 68036b08b91bc ("drm/vblank: Do not update vblank count if interrupts are already disabled.")
Fixes: 5f2f911578fb ("drm/imx: atomic phase 3 step 1: Use atomic configuration")
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.
Robert Beckett (4):
drm/vblank: warn on sending stale event
drm/imx: notify drm core before sending event during crtc disable
drm/vblank: estimate vblank while disabling vblank if interrupt
disabled
drm/imx: only send event on crtc disable if kept disabled
drivers/gpu/drm/drm_vblank.c | 33 +++++++++++++++++++++++++++++++-
drivers/gpu/drm/imx/ipuv3-crtc.c | 6 +++---
2 files changed, 35 insertions(+), 4 deletions(-)
--
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-06-25 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 17:59 Robert Beckett [this message]
2019-06-25 17:59 ` [PATCH v3 1/4] drm/vblank: warn on sending stale event Robert Beckett
2019-06-25 20:00 ` Daniel Vetter
2019-06-25 20:02 ` Daniel Vetter
2019-06-25 17:59 ` [PATCH v3 2/4] drm/imx: notify drm core before sending event during crtc disable Robert Beckett
2019-06-25 20:03 ` Daniel Vetter
2019-06-25 17:59 ` [PATCH v3 3/4] drm/vblank: estimate vblank while disabling vblank if interrupt disabled Robert Beckett
2019-06-25 20:11 ` Daniel Vetter
2019-06-26 13:27 ` Ville Syrjälä
2019-06-26 14:30 ` Daniel Vetter
2019-06-25 17:59 ` [PATCH v3 4/4] drm/imx: only send event on crtc disable if kept disabled Robert Beckett
2019-06-25 20:22 ` Daniel Vetter
2019-06-26 8:33 ` 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=cover.1561483965.git.bob.beckett@collabora.com \
--to=bob.beckett@collabora$(echo .)com \
--cc=airlied@linux$(echo .)ie \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=festevam@gmail$(echo .)com \
--cc=kernel@pengutronix$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maarten.lankhorst@linux$(echo .)intel.com \
--cc=maxime.ripard@bootlin$(echo .)com \
--cc=p.zabel@pengutronix$(echo .)de \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=sean@poorly$(echo .)run \
--cc=shawnguo@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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