public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/8] drm/i915: Some DPLL crtc->state/config cleanups etc.
Date: Tue, 10 Oct 2017 18:47:47 +0300	[thread overview]
Message-ID: <20171010154747.GT10981@intel.com> (raw)
In-Reply-To: <20170913140900.6972-1-ville.syrjala@linux.intel.com>

On Wed, Sep 13, 2017 at 05:08:52PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> This series nukes some crtc->config and crtc->state uses from the
> DPLL code. And I tossed in a few other random DPLL things I had lying around.
> 
> Ville Syrjälä (8):
>   drm/i915: Parametrize CBR_DPLLBMD_PIPE defines
>   drm/i915: Pass crtc state to i9xx_enable_pll()
>   drm/i915: Nuke the bogus kernel doc for i9xx_disable_pll()

Pushed those three to dinq. Thanks for the review.

>   drm/i915: Set output_types to EDP for vlv/chv DPLL forcing
>   drm/i915: Eliminate crtc->config from VLV/CHV DPLL functions
>   drm/i915: Add for_each_oldnew_intel_crtc_in_state()
>   drm/i915: Shrink active_crtcs and active_pipes_changed to u8
>   drm/i915: Eliminate crtc->state usage from DVO pipe tracking
> 
>  drivers/gpu/drm/i915/i915_drv.h      | 12 ++++-
>  drivers/gpu/drm/i915/i915_reg.h      |  3 +-
>  drivers/gpu/drm/i915/intel_display.c | 88 ++++++++++++++++--------------------
>  drivers/gpu/drm/i915/intel_drv.h     |  6 ++-
>  4 files changed, 56 insertions(+), 53 deletions(-)
> 
> -- 
> 2.13.5

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-10-10 15:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 14:08 [PATCH 0/8] drm/i915: Some DPLL crtc->state/config cleanups etc Ville Syrjala
2017-09-13 14:08 ` [PATCH 1/8] drm/i915: Set output_types to EDP for vlv/chv DPLL forcing Ville Syrjala
2017-09-13 14:08 ` [PATCH 2/8] drm/i915: Parametrize CBR_DPLLBMD_PIPE defines Ville Syrjala
2017-09-13 14:38   ` Chris Wilson
2017-09-13 14:08 ` [PATCH 3/8] drm/i915: Eliminate crtc->config from VLV/CHV DPLL functions Ville Syrjala
2017-09-13 14:40   ` Chris Wilson
2017-09-13 15:18     ` Ville Syrjälä
2017-09-13 14:08 ` [PATCH 4/8] drm/i915: Pass crtc state to i9xx_enable_pll() Ville Syrjala
2017-09-13 14:41   ` Chris Wilson
2017-09-13 15:20     ` Ville Syrjälä
2017-09-13 14:08 ` [PATCH 5/8] drm/i915: Nuke the bogus kernel doc for i9xx_disable_pll() Ville Syrjala
2017-09-13 14:42   ` Chris Wilson
2017-09-13 14:08 ` [PATCH 6/8] drm/i915: Add for_each_oldnew_intel_crtc_in_state() Ville Syrjala
2017-09-13 14:08 ` [PATCH 7/8] drm/i915: Shrink active_crtcs and active_pipes_changed to u8 Ville Syrjala
2017-09-13 14:49   ` Chris Wilson
2017-09-13 16:30     ` Ville Syrjälä
2017-09-13 14:09 ` [PATCH 8/8] drm/i915: Eliminate crtc->state usage from DVO pipe tracking Ville Syrjala
2017-09-13 14:51   ` Chris Wilson
2017-09-13 14:37 ` ✓ Fi.CI.BAT: success for drm/i915: Some DPLL crtc->state/config cleanups etc Patchwork
2017-09-14  1:04 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-10-10 15:47 ` 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=20171010154747.GT10981@intel.com \
    --to=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox