All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: keithp@keithp.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: load the LUT before pipe enable on ILK+
Date: Fri, 22 Jul 2011 12:54:22 -0700	[thread overview]
Message-ID: <20110722125422.3397fdcd@jbarnes-desktop> (raw)
In-Reply-To: <1308173553-2797-1-git-send-email-jbarnes@virtuousgeek.org>

On Wed, 15 Jun 2011 23:32:33 +0200
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> Per the specs and to address
> https://bugs.freedesktop.org/show_bug.cgi?id=36888.
> 
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> ---
>  drivers/gpu/drm/i915/intel_display.c |    8 ++++++--
>  1 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 81a9059..03ce9fa 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2699,14 +2699,18 @@ static void ironlake_crtc_enable(struct drm_crtc *crtc)
>  		I915_WRITE(PF_WIN_SZ(pipe), dev_priv->pch_pf_size);
>  	}
>  
> +	/*
> +	 * On ILK+ LUT must be loaded before the pipe is running but with
> +	 * clocks enabled
> +	 */
> +	intel_crtc_load_lut(crtc);
> +
>  	intel_enable_pipe(dev_priv, pipe, is_pch_port);
>  	intel_enable_plane(dev_priv, plane, pipe);
>  
>  	if (is_pch_port)
>  		ironlake_pch_enable(crtc);
>  
> -	intel_crtc_load_lut(crtc);
> -
>  	mutex_lock(&dev->struct_mutex);
>  	intel_update_fbc(dev);
>  	mutex_unlock(&dev->struct_mutex);

Keith, please pull this one in for 3.1.  Hardware will wedge if we try
to access the palette after pipe enable but before FDI or eDP training
completes, so we may as well just do it right before pipe enable.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-07-22 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 21:32 [PATCH] drm/i915: load the LUT before pipe enable on ILK+ Jesse Barnes
2011-07-22 19:54 ` Jesse Barnes [this message]
2011-07-22 20:41   ` Keith Packard

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=20110722125422.3397fdcd@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.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.