intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/4] drm/i915: deconflate display disable from no display
Date: Thu, 5 Sep 2019 15:28:08 +0300	[thread overview]
Message-ID: <20190905122808.GH7482@intel.com> (raw)
In-Reply-To: <cover.1567446845.git.jani.nikula@intel.com>

On Mon, Sep 02, 2019 at 09:08:12PM +0300, Jani Nikula wrote:
> Deconflate not having display hardware from having disabled display
> hardware, with some collateral improvements.
> 
> This doesn't actually fix any of the issues resulting from the two being
> conflated, but unblocks fixing both independently.
> 
> Read the commit messages for details.
> 
> BR,
> Jani.
> 
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>

Looks good based on a cursor scan. Series is
Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> 
> Jani Nikula (4):
>   drm/i915: add INTEL_NUM_PIPES() and use it
>   drm/i915: convert device info num_pipes to pipe_mask
>   drm/i915: introduce INTEL_DISPLAY_ENABLED()
>   drm/i915: stop conflating HAS_DISPLAY() and disabled display
> 
>  drivers/gpu/drm/i915/display/intel_bios.c     |  2 +-
>  drivers/gpu/drm/i915/display/intel_display.c  | 30 ++++++++++---------
>  drivers/gpu/drm/i915/display/intel_display.h  |  4 +--
>  drivers/gpu/drm/i915/display/intel_fbdev.c    |  2 +-
>  drivers/gpu/drm/i915/display/intel_gmbus.c    |  2 +-
>  .../gpu/drm/i915/display/intel_lpe_audio.c    |  2 +-
>  drivers/gpu/drm/i915/i915_drv.c               | 10 +++----
>  drivers/gpu/drm/i915/i915_drv.h               |  7 ++++-
>  drivers/gpu/drm/i915/i915_pci.c               | 24 +++++++--------
>  drivers/gpu/drm/i915/intel_device_info.c      | 16 ++++------
>  drivers/gpu/drm/i915/intel_device_info.h      |  2 +-
>  drivers/gpu/drm/i915/intel_pch.c              |  2 +-
>  drivers/gpu/drm/i915/intel_pm.c               |  6 ++--
>  13 files changed, 56 insertions(+), 53 deletions(-)
> 
> -- 
> 2.20.1

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

      parent reply	other threads:[~2019-09-05 12:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 18:08 [PATCH 0/4] drm/i915: deconflate display disable from no display Jani Nikula
2019-09-02 18:08 ` [PATCH 1/4] drm/i915: add INTEL_NUM_PIPES() and use it Jani Nikula
2019-09-04 23:35   ` Souza, Jose
2019-09-02 18:08 ` [PATCH 2/4] drm/i915: convert device info num_pipes to pipe_mask Jani Nikula
2019-09-04 23:35   ` Souza, Jose
2019-09-02 18:08 ` [PATCH 3/4] drm/i915: introduce INTEL_DISPLAY_ENABLED() Jani Nikula
2019-09-05  0:00   ` Souza, Jose
2019-09-02 18:08 ` [PATCH 4/4] drm/i915: stop conflating HAS_DISPLAY() and disabled display Jani Nikula
2019-09-04 23:57   ` Souza, Jose
2019-09-02 18:13 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: deconflate display disable from no display Patchwork
2019-09-02 18:37 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-09-05 12:28 ` 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=20190905122808.GH7482@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).