From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Luca Coelho <luciano.coelho@intel.com>,
Jani Nikula <jani.nikula@intel.com>
Subject: [PATCH v4 00/15] drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD
Date: Fri, 8 Nov 2024 09:57:05 -0300 [thread overview]
Message-ID: <20241108130218.24125-1-gustavo.sousa@intel.com> (raw)
Using the DMC wakelock is the official recommendation for Xe3_LPD. This
series apply fixes to the current DMC wakelock implementation and
enables it by default for Xe3_LPD. The series has been tested with a PTL
machine.
This is the v4 of the series. The only difference from v3 is that I decided to
drop patches related to the usage of HAS_DMC() in HAS_DMC_WAKELOCK(), as they
might need more polishing and will be send as a separate series. I believe we
don't need to be blocked on those to get this series landed.
Gustavo Sousa (15):
drm/i915/dmc_wl: Use i915_mmio_reg_offset() instead of reg.reg
drm/xe: Mimic i915 behavior for non-sleeping MMIO wait
drm/i915/dmc_wl: Use non-sleeping variant of MMIO wait
drm/i915/dmc_wl: Check for non-zero refcount in release work
drm/i915/dmc_wl: Get wakelock when disabling dynamic DC states
drm/i915/dmc_wl: Use sentinel item for range tables
drm/i915/dmc_wl: Extract intel_dmc_wl_reg_in_range()
drm/i915/dmc_wl: Rename lnl_wl_range to powered_off_ranges
drm/i915/dmc_wl: Track registers touched by the DMC
drm/i915/dmc_wl: Allow simpler syntax for single reg in range tables
drm/i915/dmc_wl: Deal with existing references when disabling
drm/i915/dmc_wl: Couple enable/disable with dynamic DC states
drm/i915/dmc_wl: Add and use HAS_DMC_WAKELOCK()
drm/i915/dmc_wl: Sanitize enable_dmc_wl according to hardware support
drm/i915/xe3lpd: Use DMC wakelock by default
drivers/gpu/drm/i915/display/intel_de.h | 10 +
.../drm/i915/display/intel_display_device.h | 1 +
.../drm/i915/display/intel_display_params.c | 6 +-
.../drm/i915/display/intel_display_params.h | 2 +-
.../i915/display/intel_display_power_well.c | 19 +-
drivers/gpu/drm/i915/display/intel_dmc.c | 4 -
drivers/gpu/drm/i915/display/intel_dmc_wl.c | 304 ++++++++++++++----
drivers/gpu/drm/i915/display/intel_dmc_wl.h | 13 +-
.../drm/xe/compat-i915-headers/intel_uncore.h | 11 +-
9 files changed, 295 insertions(+), 75 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-08 13:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 12:57 Gustavo Sousa [this message]
2024-11-08 12:57 ` [PATCH v4 01/15] drm/i915/dmc_wl: Use i915_mmio_reg_offset() instead of reg.reg Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 02/15] drm/xe: Mimic i915 behavior for non-sleeping MMIO wait Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 03/15] drm/i915/dmc_wl: Use non-sleeping variant of " Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 04/15] drm/i915/dmc_wl: Check for non-zero refcount in release work Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 05/15] drm/i915/dmc_wl: Get wakelock when disabling dynamic DC states Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 06/15] drm/i915/dmc_wl: Use sentinel item for range tables Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 07/15] drm/i915/dmc_wl: Extract intel_dmc_wl_reg_in_range() Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 08/15] drm/i915/dmc_wl: Rename lnl_wl_range to powered_off_ranges Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 09/15] drm/i915/dmc_wl: Track registers touched by the DMC Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 10/15] drm/i915/dmc_wl: Allow simpler syntax for single reg in range tables Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 11/15] drm/i915/dmc_wl: Deal with existing references when disabling Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 12/15] drm/i915/dmc_wl: Couple enable/disable with dynamic DC states Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 13/15] drm/i915/dmc_wl: Add and use HAS_DMC_WAKELOCK() Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 14/15] drm/i915/dmc_wl: Sanitize enable_dmc_wl according to hardware support Gustavo Sousa
2024-11-08 12:57 ` [PATCH v4 15/15] drm/i915/xe3lpd: Use DMC wakelock by default Gustavo Sousa
2024-11-08 13:51 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD (rev4) Patchwork
2024-11-08 13:51 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-08 14:05 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-08 14:16 ` [PATCH v4 00/15] drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD Luca Coelho
2024-11-08 14:19 ` Gustavo Sousa
2024-11-08 15:25 ` ✓ Fi.CI.IGT: success for drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD (rev4) Patchwork
2024-11-08 18:08 ` Matt Roper
2024-11-11 9:20 ` Jani Nikula
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=20241108130218.24125-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=luciano.coelho@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