From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Extend WaDisableIPC to all platforms.
Date: Thu, 28 Sep 2017 12:12:14 -0700 [thread overview]
Message-ID: <20170928191214.2cjbw2b72uezrynn@intel.com> (raw)
In-Reply-To: <150662537914.25220.15654864135301547768@mail.alporthouse.com>
On Thu, Sep 28, 2017 at 07:02:59PM +0000, Chris Wilson wrote:
> Quoting Rodrigo Vivi (2017-09-28 19:51:48)
> > Although Bspec state this Workaround is only relevant for SKL:All.
> >
> > The wa_database state this is needed for All platforms from SKL to CNL.
> >
> > So let's pick the safest case.
> >
> > Cc: Mahesh Kumar <mahesh1.kumar@intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_pm.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index ede871b7982e..27f9d5ab2d23 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -5828,8 +5828,8 @@ void intel_enable_ipc(struct drm_i915_private *dev_priv)
> > {
> > u32 val;
> >
> > - /* Display WA #0477 WaDisableIPC: skl */
> > - if (IS_SKYLAKE(dev_priv)) {
> > + /* Display WA #0477 WaDisableIPC: skl,kbl,bxt,glk,cfl,cnl */
> > + if (INTEL_GEN(dev_priv) <= 10) {
>
> But at that point, why not just define has_ipc as a gen10 feature?
it's already there...
> You
> can have a comment before gen9 feature that although IPC was introduced
> for gen9, it is recommended (w/a) to leave disabled.
so you mean moving this Wa from here to set has_ipc = 0 to all platforms?
Anyways I'd like to hear from Manesh about it since this basically revert
all IPC work for all platforms...
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-28 19:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 18:51 [PATCH 0/4] 2-in-1: Organize feature inheritance and disable IPC Rodrigo Vivi
2017-09-28 18:51 ` [PATCH 1/4] drm/i915/skl: Fix has_ipc on skl and document WaDisableIPC Rodrigo Vivi
2017-10-03 5:26 ` Mahesh Kumar
2017-09-28 18:51 ` [PATCH 2/4] drm/i915: Organize GEN features inheritance Rodrigo Vivi
2017-09-28 19:03 ` Chris Wilson
2017-09-28 19:09 ` Rodrigo Vivi
2017-09-28 18:51 ` [PATCH 3/4] drm/i915: Organize GLK_COLORS Rodrigo Vivi
2017-09-28 19:04 ` Chris Wilson
2017-10-02 13:02 ` Jani Nikula
2017-10-02 22:55 ` Rodrigo Vivi
2017-10-03 5:42 ` Jani Nikula
2017-09-28 18:51 ` [PATCH 4/4] drm/i915: Extend WaDisableIPC to all platforms Rodrigo Vivi
2017-09-28 19:02 ` Chris Wilson
2017-09-28 19:12 ` Rodrigo Vivi [this message]
2017-09-28 19:17 ` Chris Wilson
2017-10-03 5:27 ` Mahesh Kumar
2017-10-03 6:43 ` Rodrigo Vivi
2017-09-28 19:15 ` ✗ Fi.CI.BAT: failure for 2-in-1: Organize feature inheritance and disable IPC Patchwork
2017-09-28 19:58 ` ✓ Fi.CI.BAT: success " Patchwork
2017-09-28 20:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-10-02 23:17 ` ✓ Fi.CI.BAT: success " Patchwork
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=20170928191214.2cjbw2b72uezrynn@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=chris@chris-wilson.co.uk \
--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 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.