Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/3] Workaround updates
Date: Thu, 26 Dec 2019 20:09:04 +0200	[thread overview]
Message-ID: <51aa12c9-ed90-7eb0-3d4b-1380f25fd2bb@intel.com> (raw)
In-Reply-To: <20191226173917.GE2877816@mdroper-desk1.amr.corp.intel.com>

On 26/12/2019 19:39, Matt Roper wrote:
> On Wed, Dec 25, 2019 at 09:31:29PM +0200, Lionel Landwerlin wrote:
>> On 24/12/2019 03:20, Matt Roper wrote:
>>> A quick drive-by update for some workarounds I noticed that were
>>> added/extended to additional platforms.
>>>
>>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>>> Cc: Matt Atwood <matthew.s.atwood@intel.com>
>>> Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
>>>
>>> Matt Roper (3):
>>>     drm/i915: Extend WaDisableDARBFClkGating to icl,ehl,tgl
>>>     drm/i915: Add Wa_1408615072 and Wa_1407596294 to icl,ehl
>>>     drm/i915/tgl: Extend Wa_1408615072 to tgl
>>>
>>>    drivers/gpu/drm/i915/display/intel_display.c |  7 +++++--
>>>    drivers/gpu/drm/i915/i915_reg.h              |  7 ++++++-
>>>    drivers/gpu/drm/i915/intel_pm.c              | 12 ++++++++++++
>>>    3 files changed, 23 insertions(+), 3 deletions(-)
>>>
>> Acked-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>>
>>
>> What do you think about Wa_1407352427 for ICL?
>>
>> Sounds like it could fix some 3D hangs too.
> Yeah, looks like we need to add that one for ICL/EHL.  I'll send a
> separate patch for that one since this series is ready to merge once CI
> results come back.  Thanks for pointing it out!
>
>
> Matt


Thanks for taking that on.


One question though about those workarounds, we probably need to have 
them applied to older kernels with ICL support right?

Should they be Cc stable?


Cheers,


-Lionel


>
>>
>> -Lionel
>>

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

  reply	other threads:[~2019-12-26 18:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24  1:20 [Intel-gfx] [PATCH 0/3] Workaround updates Matt Roper
2019-12-24  1:20 ` [Intel-gfx] [PATCH 1/3] drm/i915: Extend WaDisableDARBFClkGating to icl, ehl, tgl Matt Roper
2019-12-24 16:52   ` Lucas De Marchi
2019-12-24  1:20 ` [Intel-gfx] [PATCH 2/3] drm/i915: Add Wa_1408615072 and Wa_1407596294 to icl, ehl Matt Roper
2019-12-24 17:05   ` Lucas De Marchi
2019-12-24  1:20 ` [Intel-gfx] [PATCH 3/3] drm/i915/tgl: Extend Wa_1408615072 to tgl Matt Roper
2019-12-24 17:20   ` Lucas De Marchi
2019-12-24  1:58 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Workaround updates Patchwork
2019-12-24  6:07 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Workaround updates (rev2) Patchwork
2019-12-24 17:15   ` Matt Roper
2019-12-24 17:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Workaround updates (rev3) Patchwork
2019-12-25 19:31 ` [Intel-gfx] [PATCH 0/3] Workaround updates Lionel Landwerlin
2019-12-26 17:39   ` Matt Roper
2019-12-26 18:09     ` Lionel Landwerlin [this message]
2019-12-26 18:36       ` Matt Roper
2019-12-27 10:35 ` [Intel-gfx] ✓ Fi.CI.IGT: success for Workaround updates (rev3) Patchwork
2019-12-27 18:49   ` Matt Roper

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=51aa12c9-ed90-7eb0-3d4b-1380f25fd2bb@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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