Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't clobber crtc->new_config when nothing changes
Date: Fri, 21 Nov 2014 11:57:51 -0800	[thread overview]
Message-ID: <20141121115751.7d067df4@jbarnes-hsw> (raw)
In-Reply-To: <1416596436-11708-1-git-send-email-ville.syrjala@linux.intel.com>

On Fri, 21 Nov 2014 21:00:36 +0200
ville.syrjala@linux.intel.com wrote:

> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> When doing a nop modeset we currently leave crtc->new_config point at
> the already freed temporary pipe_config. That will anger the sanity
> checks in intel_modeset_update_state() when the nop modeset gets
> followed by a GPU reset on gen3/4 where the display block gets fully
> reinitialized during the reset.
> 
> So leave crtc->new_config alone until we know a modeset is actually
> required.
> 
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/intel_display.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 853697f..3218455 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -10907,7 +10907,6 @@ intel_modeset_compute_config(struct drm_crtc *crtc,
>  	}
>  	intel_dump_pipe_config(to_intel_crtc(crtc), pipe_config,
>  			       "[modeset]");
> -	to_intel_crtc(crtc)->new_config = pipe_config;
>  
>  out:
>  	return pipe_config;
> @@ -10933,6 +10932,9 @@ static int __intel_set_mode(struct drm_crtc *crtc,
>  
>  	*saved_mode = crtc->mode;
>  
> +	if (modeset_pipes)
> +		to_intel_crtc(crtc)->new_config = pipe_config;
> +
>  	/*
>  	 * See if the config requires any additional preparation, e.g.
>  	 * to adjust global state with pipes off.  We need to do this
> @@ -11466,12 +11468,12 @@ static int intel_crtc_set_config(struct drm_mode_set *set)
>  		ret = PTR_ERR(pipe_config);
>  		goto fail;
>  	} else if (pipe_config) {
> -		if (to_intel_crtc(set->crtc)->new_config->has_audio !=
> +		if (pipe_config->has_audio !=
>  		    to_intel_crtc(set->crtc)->config.has_audio)
>  			config->mode_changed = true;
>  
>  		/* Force mode sets for any infoframe stuff */
> -		if (to_intel_crtc(set->crtc)->new_config->has_infoframe ||
> +		if (pipe_config->has_infoframe ||
>  		    to_intel_crtc(set->crtc)->config.has_infoframe)
>  			config->mode_changed = true;
>  	}

Yeah looks fine.

Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-11-21 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 19:00 [PATCH] drm/i915: Don't clobber crtc->new_config when nothing changes ville.syrjala
2014-11-21 19:57 ` Jesse Barnes [this message]
2014-11-21 20:31 ` Daniel Vetter
2014-11-24  8:57 ` [PATCH] drm/i915: Don't clobber crtc->new_config when shuang.he

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=20141121115751.7d067df4@jbarnes-hsw \
    --to=jbarnes@virtuousgeek.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox