From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Deepak S <deepak.s@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 02/14] drm/i915: Extend DSL readout fix to BDW and SKL.
Date: Thu, 5 Nov 2015 08:33:05 -0800 [thread overview]
Message-ID: <563B84C1.9050704@virtuousgeek.org> (raw)
In-Reply-To: <5638AC21.9020004@linux.intel.com>
On 11/03/2015 04:44 AM, Maarten Lankhorst wrote:
> Hey,
>
> Op 03-11-15 om 12:32 schreef Jani Nikula:
>> On Tue, 03 Nov 2015, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>>> On Tue, Nov 03, 2015 at 08:31:41AM +0100, Maarten Lankhorst wrote:
>>>> Those platforms have the same bug as haswell, and the same fix applies to them.
>> How about Broxton? IS_DDI matches that.
>>
>> Jani.
>>
> Judging from irc it's very likely it suffers from the same problem, but it would be nice if we had someone who could confirm. :)
It won't hurt (much) if we apply this workaround and it doesn't affect
BXT, so I think we may as well apply given what we know of BXT's lineage.
Jesse
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-05 16:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 7:31 [PATCH v2 00/14] Kill off intel_crtc->atomic, rework Maarten Lankhorst
2015-11-03 7:31 ` [PATCH v2 01/14] drm/i915: Use passed plane state for sprite planes, v3 Maarten Lankhorst
2015-11-03 9:22 ` Ville Syrjälä
2015-11-03 10:26 ` Maarten Lankhorst
2015-11-03 7:31 ` [PATCH v2 02/14] drm/i915: Extend DSL readout fix to BDW and SKL Maarten Lankhorst
2015-11-03 9:23 ` Ville Syrjälä
2015-11-03 11:32 ` Jani Nikula
2015-11-03 12:44 ` Maarten Lankhorst
2015-11-05 16:33 ` Jesse Barnes [this message]
2015-11-06 9:47 ` Jani Nikula
2015-11-03 7:31 ` [PATCH v2 03/14] drm/i915: Do not acquire crtc state to check clock during modeset, v2 Maarten Lankhorst
2015-11-03 10:09 ` Maarten Lankhorst
2015-11-03 7:31 ` [PATCH v2 04/14] drm/i915: Handle cdclk limits on broadwell Maarten Lankhorst
2015-11-03 7:31 ` [PATCH v2 05/14] drm/i915/bxt: Use the bypass frequency if there are no active pipes Maarten Lankhorst
2015-11-03 7:31 ` [PATCH v2 06/14] drm/i915: Update watermark related members in the crtc_state, v2 Maarten Lankhorst
2015-11-09 14:48 ` Ander Conselvan De Oliveira
2015-11-09 16:10 ` Maarten Lankhorst
2015-11-09 16:20 ` Ville Syrjälä
2015-11-03 7:31 ` [PATCH v2 07/14] drm/i915: Kill off intel_crtc->atomic.wait_vblank Maarten Lankhorst
2015-11-09 15:08 ` Ander Conselvan De Oliveira
2015-11-03 7:31 ` [PATCH v2 08/14] drm/i915: Remove intel_crtc->atomic.disable_ips Maarten Lankhorst
2015-11-09 15:28 ` Ander Conselvan De Oliveira
2015-11-03 7:31 ` [PATCH v2 09/14] drm/i915: Remove atomic.pre_disable_primary Maarten Lankhorst
2015-11-10 11:29 ` Ander Conselvan De Oliveira
2015-11-03 7:31 ` [PATCH v2 10/14] drm/i915: Remove update_sprite_watermarks Maarten Lankhorst
2015-11-03 16:58 ` Matt Roper
2015-11-03 7:31 ` [PATCH v2 11/14] drm/i915: Remove some post-commit members from intel_crtc->atomic Maarten Lankhorst
2015-11-10 12:31 ` Ander Conselvan De Oliveira
2015-11-03 7:31 ` [PATCH v2 12/14] drm/i915: Nuke fbc " Maarten Lankhorst
2015-11-10 13:21 ` Ander Conselvan De Oliveira
2015-11-03 7:31 ` [PATCH v2 13/14] drm/i915/skl: Update watermarks before the crtc is disabled Maarten Lankhorst
2015-11-03 7:31 ` [PATCH v2 14/14] drm/i915/skl: Do not allow scaling when " Maarten Lankhorst
2015-11-03 9:09 ` Ville Syrjälä
2015-11-03 10:06 ` Maarten Lankhorst
2015-11-03 10:40 ` Ville Syrjälä
2015-11-03 12:00 ` Maarten Lankhorst
2015-11-03 13:11 ` Ville Syrjälä
2015-11-17 13:59 ` Maarten Lankhorst
2015-11-17 14:19 ` Ville Syrjälä
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=563B84C1.9050704@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=deepak.s@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--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