From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 0/5] drm/i915: PCH detection cleanup
Date: Thu, 22 Jun 2017 19:55:41 +0300 [thread overview]
Message-ID: <20170622165541.GJ12629@intel.com> (raw)
In-Reply-To: <20170620130310.13245-1-ville.syrjala@linux.intel.com>
On Tue, Jun 20, 2017 at 04:03:05PM +0300, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> During the recent discusison on the PCH detection details it was
> suggested that we should just always use the top 9 bits of the
> ISA/LPC bridge device ID to detect the PCH type. Currently we use
> either 8 or 9 bits depending on the PCH type.
>
> Series available here:
> git://github.com/vsyrjala/linux.git pch_id_9bits
>
> Ville Syrjälä (5):
> drm/i915: Use HAS_PCH_CPT() everywhere
> drm/i915: s/Couar/Cougar/
> drm/i915: Document that PPT==CPT and WPT==LPT
> drm/i915: Clean up some expressions
> drm/i915: Always use 9 bits of the LPC bridge device ID for PCH
> detection
Series pushed to dinq. Thanks for the review.
>
> drivers/gpu/drm/i915/i915_drv.c | 51 ++++++++++++++++++--------------
> drivers/gpu/drm/i915/i915_drv.h | 19 +++++++-----
> drivers/gpu/drm/i915/intel_device_info.c | 2 +-
> drivers/gpu/drm/i915/intel_sdvo.c | 2 +-
> 4 files changed, 41 insertions(+), 33 deletions(-)
>
> --
> 2.13.0
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-06-22 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 13:03 [PATCH 0/5] drm/i915: PCH detection cleanup ville.syrjala
2017-06-20 13:03 ` [PATCH 1/5] drm/i915: Use HAS_PCH_CPT() everywhere ville.syrjala
2017-06-20 13:03 ` [PATCH 2/5] drm/i915: s/Couar/Cougar/ ville.syrjala
2017-06-20 13:03 ` [PATCH 3/5] drm/i915: Document that PPT==CPT and WPT==LPT ville.syrjala
2017-06-20 13:03 ` [PATCH 4/5] drm/i915: Clean up some expressions ville.syrjala
2017-06-20 13:46 ` Jani Nikula
2017-06-20 13:03 ` [PATCH 5/5] drm/i915: Always use 9 bits of the LPC bridge device ID for PCH detection ville.syrjala
2017-06-20 14:34 ` Jani Nikula
2017-06-20 14:52 ` Ville Syrjälä
2017-06-20 18:36 ` Pandiyan, Dhinakaran
2017-06-20 18:50 ` Ville Syrjälä
2017-06-21 17:49 ` [PATCH v2 " ville.syrjala
2017-06-20 13:49 ` ✗ Fi.CI.BAT: warning for drm/i915: PCH detection cleanup Patchwork
2017-06-21 18:05 ` ✓ Fi.CI.BAT: success for drm/i915: PCH detection cleanup (rev2) Patchwork
2017-06-22 16:55 ` Ville Syrjälä [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=20170622165541.GJ12629@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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