From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Joe Konno <joe.konno@intel.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: Fix IPS related flicker
Date: Fri, 22 May 2015 10:08:21 +0300 [thread overview]
Message-ID: <20150522070821.GW18908@intel.com> (raw)
In-Reply-To: <1432237983-3795-1-git-send-email-rodrigo.vivi@intel.com>
On Thu, May 21, 2015 at 12:53:03PM -0700, Rodrigo Vivi wrote:
> We cannot let IPS enabled with no plane on the pipe:
>
> BSpec: "IPS cannot be enabled until after at least one plane has
> been enabled for at least one vertical blank." and "IPS must be
> disabled while there is still at least one plane enabled on the
> same pipe as IPS.
>
> However this shortcut path to make primary plane invisible when
> updating primary plane was leting IPS enabled while there was no
> other plane enabled on the pipe causing flickerings that we were
> believing that it was caused by that other restriction where
> ips cannot be used when pixel rate is greater than 95% of cdclok.
>
> Reference: https://bugs.freedesktop.org/show_bug.cgi?id=85583
> Cc: Joe Konno <joe.konno@intel.com>
> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 9d2d6fb..5519d56 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2789,6 +2789,19 @@ static void ironlake_update_primary_plane(struct drm_crtc *crtc,
> int pixel_size;
>
> if (!visible || !fb) {
> + /*
> + * This shortcut path disables the primary plane making
> + * IPS really sad and lost when it is enabled alone with no
> + * plane around on the pipe. So, for now it is safe to disable
> + * IPS here.
> + /
> + /*
> + * FIXME: Any other plane enabled should be enough so it would
> + * be better to check if there is really no sprite or
> + * cursor around.
> + */
> + hsw_disable_ips(intel_crtc);
> +
This isn't really the right place for it. It should be called by higher
level functions outside of the atomic critical section. I suppose we're
missing it from some legacy path.
> I915_WRITE(reg, 0);
> I915_WRITE(DSPSURF(plane), 0);
> POSTING_READ(reg);
> --
> 2.1.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-22 7:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 19:53 [PATCH] drm/i915: Fix IPS related flicker Rodrigo Vivi
2015-05-21 21:33 ` Daniel Vetter
2015-05-21 21:38 ` Vivi, Rodrigo
2015-05-22 7:08 ` Ville Syrjälä [this message]
2015-05-28 18:07 ` Rodrigo Vivi
2015-05-29 8:47 ` Ville Syrjälä
[not found] ` <CABVU7+vRFgtc8GYZ+vMPZT3YcYBUKdF5wd_N2MYy4koyLdVoUg@mail.gmail.com>
2015-06-04 18:55 ` Fwd: " Rodrigo Vivi
2015-06-05 8:51 ` Jani Nikula
2015-06-05 9:11 ` Ville Syrjälä
2015-06-18 10:58 ` Ander Conselvan De Oliveira
2015-06-18 11:53 ` Jani Nikula
2015-06-18 11:58 ` Jani Nikula
2015-06-25 12:01 ` Jani Nikula
2015-06-25 16:21 ` Rodrigo Vivi
2015-06-25 16:49 ` Jani Nikula
2015-06-25 16:58 ` Rodrigo Vivi
2015-06-26 9:19 ` Daniel Vetter
2015-06-26 9:27 ` Jani Nikula
2015-06-26 20:55 ` Rodrigo Vivi
2015-05-31 14:36 ` shuang.he
2015-06-26 9:11 ` Jani Nikula
2015-05-22 7:57 ` shuang.he
2015-05-28 23:57 ` Kenneth Graunke
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=20150522070821.GW18908@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joe.konno@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@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.