From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend
Date: Thu, 26 Jan 2017 11:06:23 -0200 [thread overview]
Message-ID: <1485435983.2429.26.camel@intel.com> (raw)
In-Reply-To: <20170126130214.GC31595@intel.com>
Em Qui, 2017-01-26 às 15:02 +0200, Ville Syrjälä escreveu:
> On Thu, Jan 26, 2017 at 12:50:28PM +0000, Chris Wilson wrote:
> >
> > As we add new generations, we should keep detecting new system
> > development platforms that were temporarily enabled (via
> > "i915.alpha_support") and now superseded by production systems. To
> > make
> > it easier to add more platforms, split the if into a series of
> > logical
> > operations.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_drv.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_drv.c
> > b/drivers/gpu/drm/i915/i915_drv.c
> > index 008fc1e62a69..c2c210b0f47f 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.c
> > +++ b/drivers/gpu/drm/i915/i915_drv.c
> > @@ -782,8 +782,12 @@ static void i915_workqueues_cleanup(struct
> > drm_i915_private *dev_priv)
> > */
> > static void intel_detect_preproduction_hw(struct drm_i915_private
> > *dev_priv)
> > {
> > - if (IS_HSW_EARLY_SDV(dev_priv) ||
> > - IS_SKL_REVID(dev_priv, 0, SKL_REVID_F0))
> > + bool sdv = false;
>
> Presumably not all SDVs use pre-production silicon, so the name of
> this variable feels a bit off. Also since it doesn't actually check
> anything about the actual board we can't even say that it's an
> actual SDV, so the HSW_EARLY_SDV() macro seems somewhat poorly named
> to me as well.
The HSW case is different since those SDVs even have different PCI IDs
too, not only REV IDs, and "_SDV" is how the PCI IDs are named. I
wonder if we should just remove them from our list of PCI IDs. Could
these IDs be repurposed in the future?
>
> >
> > +
> > + sdv |= IS_HSW_EARLY_SDV(dev_priv);
> > + sdv |= IS_SKL_REVID(dev_priv, 0, SKL_REVID_F0);
> > +
> > + if (sdv)
> > DRM_ERROR("This is a pre-production stepping. "
> > "It may not be fully functional.\n");
> > }
> > --
> > 2.11.0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-26 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 12:50 [PATCH 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend Chris Wilson
2017-01-26 12:50 ` [PATCH 2/3] drm/i915: Mark the kernel as tainted if we fail the preproduction check Chris Wilson
2017-01-26 13:26 ` Jani Nikula
2017-01-26 12:50 ` [PATCH 3/3] drm/i915: Add early BXT sdv to the list of preproduction machines Chris Wilson
2017-01-26 13:02 ` [PATCH 1/3] drm/i915: Make intel_detect_preproduction_hw easier to extend Ville Syrjälä
2017-01-26 13:06 ` Paulo Zanoni [this message]
2017-01-26 13:16 ` Chris Wilson
2017-01-26 13:21 ` Chris Wilson
2017-01-26 13:18 ` Jani Nikula
2017-01-26 13:35 ` Chris Wilson
2017-01-26 13:45 ` Jani Nikula
2017-01-26 22:54 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] " 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=1485435983.2429.26.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@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 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.