Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/8] drm/i915: Move power well code to a separate file
Date: Tue, 22 Feb 2022 18:51:29 +0200	[thread overview]
Message-ID: <20220222165137.1004194-1-imre.deak@intel.com> (raw)

This is the first half of patchset [1], rebased on drm-tip and adding
the R-b tags from Jouni. I'll send the second half separately as that
needs a minor change and it's worth having a separate CI test result for
the changes there (convert the u64 domain to a bitmap, sanitize the
port/aux_ch->power domain mappings).

[1] https://patchwork.freedesktop.org/series/99476/

Cc: Jouni Högander <jouni.hogander@intel.com>

Imre Deak (8):
  drm/i915: Fix the VDSC_PW2 power domain enum value
  drm/i915: Sanitize open-coded power well enable()/disable() calls
  drm/i915: Remove redundant state verification during TypeC AUX power
    well disabling
  drm/i915: Move i915_power_well_regs struct into i915_power_well_ops
  drm/i915: Move power well get/put/enable/disable functions to a new
    file
  drm/i915: Add function to call a power well's sync_hw() hook
  drm/i915: Add functions to get a power well's
    state/name/domains/mask/refcount
  drm/i915: Move intel_display_power_well_is_enabled() to
    intel_display_power_well.c

 drivers/gpu/drm/i915/Makefile                 |   1 +
 .../drm/i915/display/intel_display_debugfs.c  |   1 +
 .../drm/i915/display/intel_display_power.c    | 521 ++++--------------
 .../drm/i915/display/intel_display_power.h    |  37 +-
 .../i915/display/intel_display_power_well.c   | 113 ++++
 .../i915/display/intel_display_power_well.h   | 153 +++++
 drivers/gpu/drm/i915/display/intel_hdcp.c     |   1 +
 7 files changed, 386 insertions(+), 441 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/display/intel_display_power_well.c
 create mode 100644 drivers/gpu/drm/i915/display/intel_display_power_well.h

-- 
2.27.0


             reply	other threads:[~2022-02-22 16:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 16:51 Imre Deak [this message]
2022-02-22 16:51 ` [Intel-gfx] [PATCH 1/8] drm/i915: Fix the VDSC_PW2 power domain enum value Imre Deak
2022-02-22 16:51 ` [Intel-gfx] [PATCH 2/8] drm/i915: Sanitize open-coded power well enable()/disable() calls Imre Deak
2022-02-22 16:51 ` [Intel-gfx] [PATCH 3/8] drm/i915: Remove redundant state verification during TypeC AUX power well disabling Imre Deak
2022-02-22 16:51 ` [Intel-gfx] [PATCH 4/8] drm/i915: Move i915_power_well_regs struct into i915_power_well_ops Imre Deak
2022-02-22 16:51 ` [Intel-gfx] [PATCH 5/8] drm/i915: Move power well get/put/enable/disable functions to a new file Imre Deak
2022-02-22 16:51 ` [Intel-gfx] [PATCH 6/8] drm/i915: Add function to call a power well's sync_hw() hook Imre Deak
2022-02-22 16:51 ` [Intel-gfx] [PATCH 7/8] drm/i915: Add functions to get a power well's state/name/domains/mask/refcount Imre Deak
2022-02-22 16:51 ` [Intel-gfx] [PATCH 8/8] drm/i915: Move intel_display_power_well_is_enabled() to intel_display_power_well.c Imre Deak
2022-02-23  0:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Move power well code to a separate file Patchwork
2022-02-23  0:18 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-23  0:49 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-23 23:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Move power well code to a separate file (rev2) Patchwork
2022-02-23 23:51 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-24  0:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-24 12:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-25 19:22   ` Imre Deak
2022-02-26  6:12     ` Vudum, Lakshminarayana
2022-02-26  3:40 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=20220222165137.1004194-1-imre.deak@intel.com \
    --to=imre.deak@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