All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lyude Paul <lyude@redhat.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: Check for I915_MODE_FLAG_INHERITED before drm_atomic_helper_check_modeset
Date: Wed, 21 Feb 2018 18:12:51 -0500	[thread overview]
Message-ID: <1519254771.3735.25.camel@redhat.com> (raw)
In-Reply-To: <20180221092808.30060-1-maarten.lankhorst@linux.intel.com>

Nice, this is a no-brainer

Reviewed-by: Lyude Paul <lyude@redhat.com>

On Wed, 2018-02-21 at 10:28 +0100, Maarten Lankhorst wrote:
> Moving the check upwards will mean we we no longer have to add planes
> and connectors manually, because everything is handled correctly by
> drm_atomic_helper_check_modeset() as intended.
> 
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Lyude Paul <lyude@redhat.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
>  drivers/gpu/drm/i915/intel_display.c | 20 +++++---------------
>  1 file changed, 5 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index 65be7af7f647..c5cc9022d545 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -11927,6 +11927,11 @@ static int intel_atomic_check(struct drm_device
> *dev,
>  	int ret, i;
>  	bool any_ms = false;
>  
> +	/* Catch I915_MODE_FLAG_INHERITED */
> +	for_each_oldnew_crtc_in_state(state, crtc, old_crtc_state,
> crtc_state, i)
> +		if (crtc_state->mode.private_flags != old_crtc_state-
> >mode.private_flags)
> +			crtc_state->mode_changed = true;
> +
>  	ret = drm_atomic_helper_check_modeset(dev, state);
>  	if (ret)
>  		return ret;
> @@ -11935,10 +11940,6 @@ static int intel_atomic_check(struct drm_device
> *dev,
>  		struct intel_crtc_state *pipe_config =
>  			to_intel_crtc_state(crtc_state);
>  
> -		/* Catch I915_MODE_FLAG_INHERITED */
> -		if (crtc_state->mode.private_flags != old_crtc_state-
> >mode.private_flags)
> -			crtc_state->mode_changed = true;
> -
>  		if (!needs_modeset(crtc_state))
>  			continue;
>  
> @@ -11947,13 +11948,6 @@ static int intel_atomic_check(struct drm_device
> *dev,
>  			continue;
>  		}
>  
> -		/* FIXME: For only active_changed we shouldn't need to do
> any
> -		 * state recomputation at all. */
> -
> -		ret = drm_atomic_add_affected_connectors(state, crtc);
> -		if (ret)
> -			return ret;
> -
>  		ret = intel_modeset_pipe_config(crtc, pipe_config);
>  		if (ret) {
>  			intel_dump_pipe_config(to_intel_crtc(crtc),
> @@ -11972,10 +11966,6 @@ static int intel_atomic_check(struct drm_device
> *dev,
>  		if (needs_modeset(crtc_state))
>  			any_ms = true;
>  
> -		ret = drm_atomic_add_affected_planes(state, crtc);
> -		if (ret)
> -			return ret;
> -
>  		intel_dump_pipe_config(to_intel_crtc(crtc), pipe_config,
>  				       needs_modeset(crtc_state) ?
>  				       "[modeset]" : "[fastset]");
-- 
Cheers,
	Lyude Paul
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-02-21 23:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21  9:28 [PATCH] drm/i915: Check for I915_MODE_FLAG_INHERITED before drm_atomic_helper_check_modeset Maarten Lankhorst
2018-02-21  9:40 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-02-21  9:55 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-02-21 12:40 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2018-02-21 12:54 ` ✗ Fi.CI.BAT: " Patchwork
2018-02-21 23:12 ` Lyude Paul [this message]
2018-03-02  2:03 ` [PATCH] " Lyude Paul
2018-03-02  9:37   ` Jani Nikula
2018-03-02 10:14     ` Lofstedt, Marta
2018-03-02 19:59 ` ✗ Fi.CI.BAT: failure for " Patchwork

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=1519254771.3735.25.camel@redhat.com \
    --to=lyude@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.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 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.