public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ander Conselvan de Oliveira <conselvan2@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: calculate pfit changes in set_config v3
Date: Mon, 17 Nov 2014 11:08:58 +0200	[thread overview]
Message-ID: <5469BB2A.8090306@gmail.com> (raw)
In-Reply-To: <1415737847-1925-2-git-send-email-jbarnes@virtuousgeek.org>

On 11/11/2014 10:30 PM, Jesse Barnes wrote:
> This should allow us to avoid mode sets for some panel fitter config
> changes.
> 
> v2:
>    - fixup pfit comment (Ander)
> v3:
>    - fixup pfit disable shortcut, only apply to gen4 for now (Jesse)

I see that the patch does what it claims it does, so you can use the 
following r-b tag. However, I want to point out that all the 
documentation I came across, including for PCH platforms, state that 
the proper modeset order is to enable pfit before the pipe is enabled 
and to disable it after disabling the pipe. So I assume you know better 
than the docs.

Reviewed-by: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>

> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> ---
>   drivers/gpu/drm/i915/intel_display.c | 73 ++++++++++++++++++++++++++++++------
>   1 file changed, 62 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 58ed4ef..e7175b1 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2861,17 +2861,8 @@ static void intel_update_pipe_size(struct intel_crtc *crtc)
>   		return;
>   
>   	/*
> -	 * Update pipe size and adjust fitter if needed: the reason for this is
> -	 * that in compute_mode_changes we check the native mode (not the pfit
> -	 * mode) to see if we can flip rather than do a full mode set. In the
> -	 * fastboot case, we'll flip, but if we don't update the pipesrc and
> -	 * pfit state, we'll end up with a big fb scanned out into the wrong
> -	 * sized surface.
> -	 *
> -	 * To fix this properly, we need to hoist the checks up into
> -	 * compute_mode_changes (or above), check the actual pfit state and
> -	 * whether the platform allows pfit disable with pipe active, and only
> -	 * then update the pipesrc and pfit state, even on the flip path.
> +	 * See intel_pfit_changed for info on when we're allowed to
> +	 * do this w/o a pipe shutdown.
>   	 */
>   
>   	adjusted_mode = &crtc->config.adjusted_mode;
> @@ -11266,6 +11257,62 @@ static void disable_crtc_nofb(struct intel_crtc *crtc)
>   	crtc->new_config = NULL;
>   }
>   
> +/* Do we need a mode set due to pfit changes? */
> +static bool intel_pfit_changed(struct drm_device *dev,
> +			       struct intel_crtc_config *new_config,
> +			       struct intel_crtc_config *cur_config)
> +{
> +	bool ret = false;
> +
> +	if (HAS_DDI(dev) || HAS_PCH_SPLIT(dev)) {
> +		/*
> +		 * On PCH platforms we can disable pfit w/o a pipe shutdown,
> +		 * otherwise we'll need a mode set.
> +		 */
> +		if (new_config->pch_pfit.enabled &&
> +		    cur_config->pch_pfit.enabled)
> +			ret = false;
> +		else if (new_config->pch_pfit.enabled &&
> +			 !cur_config->pch_pfit.enabled)
> +			ret = true;
> +		else if (!new_config->pch_pfit.enabled &&
> +			 cur_config->pch_pfit.enabled)
> +			ret = false;
> +		else if (!new_config->pch_pfit.enabled &&
> +			 !cur_config->pch_pfit.enabled)
> +			ret = false;
> +	} else if (IS_GEN4(dev)) {
> +		/*
> +		 * We may be able to get away with this on more chips, but
> +		 * we need more testing here.
> +		 */
> +		bool new_enabled, old_enabled;
> +
> +		new_enabled = !!(new_config->gmch_pfit.control & PFIT_ENABLE);
> +		old_enabled = !!(cur_config->gmch_pfit.control & PFIT_ENABLE);
> +
> +		/* 9xx only needs a shutdown to disable pfit */
> +		if (new_enabled && old_enabled)
> +			ret = false;
> +		else if (new_enabled && !old_enabled)
> +			ret = false;
> +		else if (!new_enabled && old_enabled)
> +			ret = true;
> +		else if (!new_enabled && !old_enabled)
> +			ret = false;
> +	} else {
> +		bool new_enabled, old_enabled;
> +
> +		new_enabled = !!(new_config->gmch_pfit.control & PFIT_ENABLE);
> +		old_enabled = !!(cur_config->gmch_pfit.control & PFIT_ENABLE);
> +
> +		if (new_enabled != old_enabled)
> +			ret = true;
> +	}
> +
> +	return ret;
> +}
> +
>   static int intel_crtc_set_config(struct drm_mode_set *set)
>   {
>   	struct drm_device *dev;
> @@ -11334,6 +11381,10 @@ static int intel_crtc_set_config(struct drm_mode_set *set)
>   		if (to_intel_crtc(set->crtc)->new_config->has_infoframe ||
>   		    to_intel_crtc(set->crtc)->config.has_infoframe)
>   			config->mode_changed = true;
> +
> +		if (intel_pfit_changed(dev, to_intel_crtc(set->crtc)->new_config,
> +				       &to_intel_crtc(set->crtc)->config))
> +			config->mode_changed = true;
>   	}
>   
>   	/* set_mode will free it in the mode_changed case */
> 

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2014-11-17  9:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 20:30 [PATCH 1/2] drm/i915/hdmi: fetch infoframe status in get_config v3 Jesse Barnes
2014-11-11 20:30 ` [PATCH 2/2] drm/i915: calculate pfit changes in set_config v3 Jesse Barnes
2014-11-12 15:41   ` [PATCH 2/2] drm/i915: calculate pfit changes in shuang.he
2014-11-17  9:08   ` Ander Conselvan de Oliveira [this message]
2014-12-09 17:51   ` [PATCH 2/2] drm/i915: calculate pfit changes in set_config v3 Jesse Barnes
2014-12-09 21:16     ` Daniel Vetter
2014-12-09 21:28       ` Jesse Barnes
2014-12-09 21:59         ` Daniel Vetter
2014-11-12  9:44 ` [PATCH 1/2] drm/i915/hdmi: fetch infoframe status in get_config v3 Daniel Vetter

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=5469BB2A.8090306@gmail.com \
    --to=conselvan2@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    /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