From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "airlied@linux.ie" <airlied@linux.ie>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Redefine some Whiskey Lake SKUs
Date: Fri, 5 Oct 2018 14:00:29 -0700 [thread overview]
Message-ID: <20181005210028.GD16191@intel.com> (raw)
In-Reply-To: <109b1f6d495f46ae6d822134f5a5212054990127.camel@intel.com>
On Tue, Sep 25, 2018 at 08:08:59PM +0000, Souza, Jose wrote:
> On Mon, 2018-09-24 at 16:43 -0700, Rodrigo Vivi wrote:
> > commit 'b9be78531d27 ("drm/i915/whl: Introducing
> > Whiskey Lake platform")' introduced WHL by moving some
> > of CFL IDs here and using the Spec information of "U43" for
> > most of IDs what appeared to be GT3.
> >
> > However when propagating the change to Mesa, Lionel noticed
> > that based on number of execution unities the classification
> > here seems at least strange.
> >
> > So, let's move for now with the information we trust more:
> > the number of EUs. So we are able to propagate this change
> > across the stack without getting stuck forever.
> >
> > Reference: https://patchwork.freedesktop.org/patch/246695/
> > Fixes: b9be78531d27 ("drm/i915/whl: Introducing Whiskey Lake
> > platform")
> > Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>
> By the EU number this looks right.
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
pushed to dinq, thanks
>
> > Cc: José Roberto de Souza <jose.souza@intel.com>
> > Cc: David Airlie <airlied@linux.ie>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > include/drm/i915_pciids.h | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> > index fd965ffbb92e..c8d3d541ad01 100644
> > --- a/include/drm/i915_pciids.h
> > +++ b/include/drm/i915_pciids.h
> > @@ -407,17 +407,17 @@
> >
> > /* WHL/CFL U GT1 */
> > #define INTEL_WHL_U_GT1_IDS(info) \
> > - INTEL_VGA_DEVICE(0x3EA1, info)
> > + INTEL_VGA_DEVICE(0x3EA1, info), \
> > + INTEL_VGA_DEVICE(0x3EA4, info)
> >
> > /* WHL/CFL U GT2 */
> > #define INTEL_WHL_U_GT2_IDS(info) \
> > - INTEL_VGA_DEVICE(0x3EA0, info)
> > + INTEL_VGA_DEVICE(0x3EA0, info), \
> > + INTEL_VGA_DEVICE(0x3EA3, info)
> >
> > /* WHL/CFL U GT3 */
> > #define INTEL_WHL_U_GT3_IDS(info) \
> > - INTEL_VGA_DEVICE(0x3EA2, info), \
> > - INTEL_VGA_DEVICE(0x3EA3, info), \
> > - INTEL_VGA_DEVICE(0x3EA4, info)
> > + INTEL_VGA_DEVICE(0x3EA2, info)
> >
> > #define INTEL_CFL_IDS(info) \
> > INTEL_CFL_S_GT1_IDS(info), \
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-10-05 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 23:43 [PATCH] drm/i915: Redefine some Whiskey Lake SKUs Rodrigo Vivi
2018-09-25 0:32 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-09-25 1:31 ` ✓ Fi.CI.IGT: " Patchwork
2018-09-25 20:08 ` [PATCH] " Souza, Jose
2018-10-05 21:00 ` Rodrigo Vivi [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=20181005210028.GD16191@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@linux.ie \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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