From: Matt Roper <matthew.d.roper@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Fwd: [linux] drm/i915: Eliminate usage of plane_wm_parameters from ILK-style WM code (v2) (43d59ed)
Date: Mon, 1 Feb 2016 01:50:43 -0800 [thread overview]
Message-ID: <20160201095043.GF20935@intel.com> (raw)
In-Reply-To: <CAKMK7uGkErCABOsSA3tbEdRh4EhraT1ntqtcgSqWsKeP-OixqA@mail.gmail.com>
On Sat, Jan 30, 2016 at 07:50:03PM -0800, Daniel Vetter wrote:
> It's a github comment so pretty hopeless to follow up with the reporter,
> but it sounds like we have a culprit for the ilk wm issues/fifo underruns.
> -Daniel
I think this is the flickering regression that we expected to come back
when we reverted the two-step watermarks. Resurrecting a much earlier
workaround that we lost should help prevent the user-visible problems in
the short term; I just sent a patch for that.
I'm traveling, so I haven't seen any IRC discussion that may have
happened recently, but I believe the CI regression we saw on that final
two-step watermark patch are still unsolved. But since we've already
reverted that patch, they shouldn't be blocking anything, right?
Matt
>
> ---------- Forwarded message ----------
> From: Manfred G Kitzbichler <notifications@github.com>
> Date: Sat, Jan 30, 2016 at 5:42 AM
> Subject: Re: [linux] drm/i915: Eliminate usage of plane_wm_parameters from
> ILK-style WM code (v2) (43d59ed)
> To: torvalds/linux <linux@noreply.github.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>
>
> As stated above, this commit introduced a screen flicker regression. Please
> fix asap!
>
> (cf.
> http://cgit.freedesktop.org/drm-intel/commit/?id=54da691deb123c045259ebf4f5c67381244f58f1
> )
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/torvalds/linux/commit/43d59eda1f69631c267e06ab6b94ed3c14f1f6d1#commitcomment-15780006>
> .
>
>
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-02-01 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <torvalds/linux/commit/43d59eda1f69631c267e06ab6b94ed3c14f1f6d1@github.com>
[not found] ` <torvalds/linux/commit/43d59eda1f69631c267e06ab6b94ed3c14f1f6d1/15780006@github.com>
2016-01-31 3:50 ` Fwd: [linux] drm/i915: Eliminate usage of plane_wm_parameters from ILK-style WM code (v2) (43d59ed) Daniel Vetter
2016-01-31 13:49 ` Jani Nikula
2016-02-01 9:50 ` Matt Roper [this message]
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=20160201095043.GF20935@intel.com \
--to=matthew.d.roper@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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