From: Thomas Hellstrom <thellstrom@vmware.com>
To: Deepak Rawat <drawat@vmware.com>,
dri-devel@lists.freedesktop.org,
linux-graphics-maintainer@vmware.com, syeh@vmware.com
Subject: Re: [PATCH v3 10/18] drm/vmwgfx: Updated comment for stdu plane update
Date: Mon, 15 Oct 2018 15:09:02 +0200 [thread overview]
Message-ID: <8375ccec-c074-a07d-499a-9c07c9e5257b@vmware.com> (raw)
In-Reply-To: <20181011001657.1715-10-drawat@vmware.com>
On 10/11/2018 02:16 AM, Deepak Rawat wrote:
> Update the commet to sync with code.
Minor typo above^
>
> Signed-off-by: Deepak Rawat <drawat@vmware.com>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 18 +++---------------
> 1 file changed, 3 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c b/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c
> index 64d11af2b81b..1821c4be0ef4 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c
> @@ -1653,7 +1653,6 @@ static int vmw_stdu_plane_update_surface(struct vmw_private *dev_priv,
>
> /**
> * vmw_stdu_primary_plane_atomic_update - formally switches STDU to new plane
> - *
> * @plane: display plane
> * @old_state: Only used to get crtc info
> *
> @@ -1674,10 +1673,7 @@ vmw_stdu_primary_plane_atomic_update(struct drm_plane *plane,
> struct vmw_private *dev_priv;
> int ret;
>
> - /*
> - * We cannot really fail this function, so if we do, then output an
> - * error and maintain consistent atomic state.
> - */
> + /* If somehow gets a device error, maintain consistent atomic state */
Perhaps: "If we somehow get", or "In case of"
> if (crtc && plane->state->fb) {
> struct vmw_framebuffer *vfb =
> vmw_framebuffer_to_vfb(plane->state->fb);
> @@ -1706,12 +1702,7 @@ vmw_stdu_primary_plane_atomic_update(struct drm_plane *plane,
> stdu = vmw_crtc_to_stdu(crtc);
> dev_priv = vmw_priv(crtc->dev);
>
> - /*
> - * When disabling a plane, CRTC and FB should always be NULL
> - * together, otherwise it's an error.
> - * Here primary plane is being disable so blank the screen
> - * target display unit, if not already done.
> - */
> + /* Blank STDU when fb and crtc are NULL */
> if (!stdu->defined)
> return;
>
> @@ -1726,11 +1717,8 @@ vmw_stdu_primary_plane_atomic_update(struct drm_plane *plane,
> return;
> }
>
> + /* In case of error vblank event is sent in vmw_du_crtc_atomic_flush */
> event = crtc->state->event;
> - /*
> - * In case of failure and other cases, vblank event will be sent in
> - * vmw_du_crtc_atomic_flush.
> - */
> if (event && fence) {
> struct drm_file *file_priv = event->base.file_priv;
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-15 13:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 0:16 [PATCH v3 01/18] drm: Add a new plane property to send damage during plane update Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 02/18] drm: Add a new helper to validate damage during atomic_check Deepak Rawat
2018-10-15 22:01 ` Sinclair Yeh
2018-10-11 0:16 ` [PATCH v3 03/18] drm: Add helper iterator functions for plane fb_damage_clips blob Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 04/18] drm/selftest: Add drm damage helper selftest Deepak Rawat
2018-10-11 16:23 ` Daniel Vetter
2018-10-15 16:11 ` Deepak Singh Rawat
2018-10-16 12:21 ` Daniel Vetter
2018-10-16 12:52 ` Alexandru-Cosmin Gheorghe
2018-10-16 16:14 ` Deepak Singh Rawat
2018-10-16 16:00 ` Deepak Singh Rawat
2018-10-11 0:16 ` [PATCH v3 05/18] drm: Add helper to implement legacy dirtyfb Deepak Rawat
2018-10-11 16:15 ` Daniel Vetter
2018-10-11 16:21 ` Daniel Vetter
2018-10-11 0:16 ` [PATCH v3 06/18] drm/vmwgfx: Add a new interface for plane update on a display unit Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 07/18] drm/vmwgfx: Implement STDU plane update for surface backed fb Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 08/18] drm/vmwgfx: Implement STDU plane update for BO " Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 09/18] drm/vmwgfx: Use the new interface for STDU plane update Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 10/18] drm/vmwgfx: Updated comment for stdu " Deepak Rawat
2018-10-15 13:09 ` Thomas Hellstrom [this message]
2018-10-11 0:16 ` [PATCH v3 11/18] drm/vmwgfx: Enable FB_DAMAGE_CLIPS property for STDU primary plane Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 12/18] drm/vmwgfx: Implement SOU plane update for surface backed fb Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 13/18] drm/vmwgfx: Implement SOU plane update for BO " Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 14/18] drm/vmwgfx: Use the new interface for SOU plane update Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 15/18] drm/vmwgfx: Update comments for sou plane update function Deepak Rawat
2018-10-15 13:10 ` Thomas Hellstrom
2018-10-11 0:16 ` [PATCH v3 16/18] drm/vmwgfx: Enable FB_DAMAGE_CLIPS property for SOU primary plane Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 17/18] drm/vmwgfx: Use atomic helper function for dirty fb IOCTL Deepak Rawat
2018-10-11 0:16 ` [PATCH v3 18/18] drm/vmwgfx: Don't clear mode::type anymore Deepak Rawat
2018-10-15 13:12 ` Thomas Hellstrom
2018-10-15 13:15 ` [PATCH v3 01/18] drm: Add a new plane property to send damage during plane update Thomas Hellstrom
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=8375ccec-c074-a07d-499a-9c07c9e5257b@vmware.com \
--to=thellstrom@vmware.com \
--cc=drawat@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=syeh@vmware.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