All of lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/bxt: update list of PCIIDs
Date: Mon, 01 Feb 2016 12:44:59 +0200	[thread overview]
Message-ID: <1454323499.31767.31.camel@intel.com> (raw)
In-Reply-To: <20160201002054.GE20935@intel.com>

On su, 2016-01-31 at 16:20 -0800, Matt Roper wrote:
> On Thu, Jan 28, 2016 at 04:04:12PM +0200, Imre Deak wrote:
> > Add PCIIDs for new versions of the SOC, based on BSpec. Also add
> > the
> > name of the versions as code comment where this is available. The
> > new
> > versions don't have any changes visible to the kernel driver.
> > 
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> >  include/drm/i915_pciids.h | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
> > index f970209..9b48ac1 100644
> > --- a/include/drm/i915_pciids.h
> > +++ b/include/drm/i915_pciids.h
> > @@ -296,7 +296,9 @@
> >  #define INTEL_BXT_IDS(info) \
> >  	INTEL_VGA_DEVICE(0x0A84, info), \
> >  	INTEL_VGA_DEVICE(0x1A84, info), \
> > -	INTEL_VGA_DEVICE(0x5A84, info)
> > +	INTEL_VGA_DEVICE(0x1A85, info), \
> 
> I don't see 0x1A85 in the bspec (at least not in the "Configurations
> ->
> Steppings and Device IDs" section...is there another list elsewhere
> in
> the bspec you got it from?)

Hm yes, it looks like it was left out from the first table, it is only
listed under "Broxton SKUs and Device IDs". I opened a new issue on the
relevant BSpec page.

> Semi-related...the revision ID vs stepping info on that page doesn't
> seem to quite match what we have in bxt_stepping_info[] in
> intel_csr.c

Hm good point. This depends on how the firmware versions will be
packaged for the newer versions. It is possible that for the new
steppings a default entry will be used, in which case we wouldn't have
to encode the individual steppings.

+Animesh. Animesh could you check the above and follow-up with a patch
updating the table if necessary?

> (plus it looks like we have some new revision ID's we could add in
> general).

The way we did this so far is to add encodings only for steppings that
we need for a WA. There hasn't been any need for the newer steppings
based on this.

--Imre


> Matt
> 
> > +	INTEL_VGA_DEVICE(0x5A84, info), /* APL HD Graphics 505 */
> > \
> > +	INTEL_VGA_DEVICE(0x5A85, info)  /* APL HD Graphics 500 */
> >  
> >  #define INTEL_KBL_GT1_IDS(info)	\
> >  	INTEL_VGA_DEVICE(0x5913, info), /* ULT GT1.5 */ \
> > -- 
> > 2.5.0
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2016-02-01 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 14:04 [PATCH] drm/i915/bxt: update list of PCIIDs Imre Deak
2016-01-28 16:03 ` Mika Kuoppala
2016-01-29 10:14 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-02-02 16:32   ` Imre Deak
2016-02-01  0:20 ` [PATCH] " Matt Roper
2016-02-01 10:44   ` Imre Deak [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=1454323499.31767.31.camel@intel.com \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 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.