From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 6/6] drm/i915: Remove IS_ULT()
Date: Wed, 1 Oct 2014 20:04:18 +0100 [thread overview]
Message-ID: <1412190258-4152-7-git-send-email-damien.lespiau@intel.com> (raw)
In-Reply-To: <1412190258-4152-1-git-send-email-damien.lespiau@intel.com>
As stated in the few previous commits, IS_ULT/ULX() is better
per-platform as it has different consequences depending on the platform.
We now can get rid of it.
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 4518f06..402673e 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -2107,7 +2107,6 @@ struct drm_i915_cmd_table {
(INTEL_DEVID(dev) & 0x00F0) == 0x0020)
#define IS_HSW_ULT(dev) (IS_HASWELL(dev) && \
(INTEL_DEVID(dev) & 0xFF00) == 0x0A00)
-#define IS_ULT(dev) (IS_HSW_ULT(dev) || IS_BDW_ULT(dev))
#define IS_HSW_GT3(dev) (IS_HASWELL(dev) && \
(INTEL_DEVID(dev) & 0x00F0) == 0x0020)
/* ULX machines are also considered ULT. */
--
1.8.3.1
next prev parent reply other threads:[~2014-10-01 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 19:04 [PATCH 0/6] Kill IS_ULT() in favour of the per-product variant Damien Lespiau
2014-10-01 19:04 ` [PATCH 1/6] drm/i915: Use IS_HSW_ULT() in a HSW specific code path Damien Lespiau
2014-10-01 19:04 ` [PATCH 2/6] drm/i915: Use IS_HSW_ULT() in HAS_IPS() Damien Lespiau
2014-10-01 19:04 ` [PATCH 3/6] drm/i915: Spell out IS_HSW/BDW_ULT() in intel_crt_present() Damien Lespiau
2014-10-01 19:04 ` [PATCH 4/6] drm/i915: Use IS_HSW_ULT() in HSW CDCLK clock read-out Damien Lespiau
2014-10-01 19:04 ` [PATCH 5/6] drm/i915/skl: Don't check for ULT/ULX when detecting the PCH Damien Lespiau
2014-10-01 19:04 ` Damien Lespiau [this message]
2014-10-01 20:36 ` [PATCH 0/6] Kill IS_ULT() in favour of the per-product variant Daniel Vetter
2014-10-03 18:40 ` Paulo Zanoni
2014-10-03 18:46 ` Paulo Zanoni
2014-10-03 18:52 ` Paulo Zanoni
2014-10-03 21:34 ` Daniel Vetter
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=1412190258-4152-7-git-send-email-damien.lespiau@intel.com \
--to=damien.lespiau@intel.com \
--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.