From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: tomi.valkeinen@ti.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] Revert "drm: omapdrm: Let the DRM core skip plane commit on inactive CRTCs"
Date: Sat, 28 Jan 2017 18:11:54 +0200 [thread overview]
Message-ID: <1633511.8VzXcN818D@avalon> (raw)
In-Reply-To: <4e28061a55b9473631f0793e1a056fcda8163508.1485510281.git.jsarha@ti.com>
Hi Jyri,
Thank you for the patch.
On Friday 27 Jan 2017 12:04:54 Jyri Sarha wrote:
> This reverts commit dadf4659d0608e034b6633f30300c2eff2dafb4c.
>
> If planes are not disabled when the they are not on any crtc anymore
> they will remain active and may show as "ghosts" when the crtc they
> were last on is active again.
Sorry for the breakage.
The drm_atomic_helper_commit_planes() helper documentation states
* Unless otherwise needed, drivers are advised to set the ACTIVE_ONLY flag in
* @flags in order not to receive plane update notifications related to a
* disabled CRTC. This avoids the need to manually ignore plane updates in
* driver code when the driver and/or hardware can't or just don't need to
* deal with updates on disabled CRTCs, for example when supporting runtime
* PM.
I wonder what this implies when CRTCs are being disabled. I see very few cases
where the hardware wouldn't need the plane atomic disable operation being
called when a plane is being disabled due to its CRTC being disabled. Maybe
this should thus be addressed in the core. Daniel, any comment on this ?
> Signed-off-by: Jyri Sarha <jsarha@ti.com>
> ---
> drivers/gpu/drm/omapdrm/omap_crtc.c | 8 +-------
> drivers/gpu/drm/omapdrm/omap_drv.c | 3 +--
> 2 files changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/omapdrm/omap_crtc.c
> b/drivers/gpu/drm/omapdrm/omap_crtc.c index dd47dc1..b68c70e 100644
> --- a/drivers/gpu/drm/omapdrm/omap_crtc.c
> +++ b/drivers/gpu/drm/omapdrm/omap_crtc.c
> @@ -410,13 +410,7 @@ static void omap_crtc_atomic_flush(struct drm_crtc
> *crtc, dispc_mgr_set_gamma(omap_crtc->channel, lut, length);
> }
>
> - /*
> - * Only flush the CRTC if it is currently enabled. CRTCs that require
a
> - * mode set are disabled prior plane updates and enabled afterwards.
> - * They are thus not active (regardless of what their CRTC core state
> - * reports) and the DRM core could thus call this function even though
> - * the CRTC is currently disabled. Do nothing in that case.
> - */
> + /* Only flush the CRTC if it is currently enabled. */
> if (!omap_crtc->enabled)
> return;
>
> diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c
> b/drivers/gpu/drm/omapdrm/omap_drv.c index 00aa214..5e55f1b 100644
> --- a/drivers/gpu/drm/omapdrm/omap_drv.c
> +++ b/drivers/gpu/drm/omapdrm/omap_drv.c
> @@ -96,8 +96,7 @@ static void omap_atomic_complete(struct
> omap_atomic_state_commit *commit) dispc_runtime_get();
>
> drm_atomic_helper_commit_modeset_disables(dev, old_state);
> - drm_atomic_helper_commit_planes(dev, old_state,
> - DRM_PLANE_COMMIT_ACTIVE_ONLY);
> + drm_atomic_helper_commit_planes(dev, old_state, 0);
> drm_atomic_helper_commit_modeset_enables(dev, old_state);
>
> omap_atomic_wait_for_completion(dev, old_state);
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-28 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 10:04 [PATCH 0/2] drm/omapdrm: Couple of plane related fixes Jyri Sarha
2017-01-27 10:04 ` [PATCH 1/2] Revert "drm: omapdrm: Let the DRM core skip plane commit on inactive CRTCs" Jyri Sarha
2017-01-28 16:11 ` Laurent Pinchart [this message]
2017-01-30 8:48 ` Tomi Valkeinen
2017-01-27 10:04 ` [PATCH 2/2] drm/omapdrm: Move commit_modeset_enables() before commit_planes() Jyri Sarha
2017-01-28 16:17 ` Laurent Pinchart
2017-01-30 8:50 ` Tomi Valkeinen
2017-01-30 11:11 ` Jyri Sarha
2017-01-30 11:15 ` Laurent Pinchart
2017-01-30 12:50 ` Jyri Sarha
2017-02-06 11:50 ` [PATCH 0/2] drm/omapdrm: Couple of plane related fixes Tomi Valkeinen
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=1633511.8VzXcN818D@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=tomi.valkeinen@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox