From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, imre.deak@intel.com
Subject: [PATCH 0/7] drm/i915/display: power conversion to struct intel_display
Date: Wed, 27 Nov 2024 19:06:01 +0200 [thread overview]
Message-ID: <cover.1732727056.git.jani.nikula@intel.com> (raw)
Lay the groundwork for display power code conversion to struct
intel_display. This still falls short for converting all the users of
power get/put/etc. but starts off with internal conversions and the high
level interfaces. It's a good start anyway.
BR,
Jani.
Jani Nikula (7):
drm/i915/display: simplify conditional compilation on runtime PM debug
drm/i915/display: convert for_each_power_well() to struct
intel_display
drm/i915/display: convert for_each_power_domain_well() to struct
intel_display
drm/i915/display: convert power wells to struct intel_display
drm/i915/display: convert power domain code internally to struct
intel_display
drm/i915/display: convert high level power interfaces to struct
intel_display
drm/i915/display: convert power map to struct intel_display
.../drm/i915/display/intel_display_debugfs.c | 3 +-
.../drm/i915/display/intel_display_driver.c | 8 +-
.../gpu/drm/i915/display/intel_display_irq.c | 3 +-
.../drm/i915/display/intel_display_power.c | 983 +++++++++---------
.../drm/i915/display/intel_display_power.h | 87 +-
.../i915/display/intel_display_power_map.c | 56 +-
.../i915/display/intel_display_power_well.c | 546 +++++-----
.../i915/display/intel_display_power_well.h | 35 +-
drivers/gpu/drm/i915/display/intel_dpio_phy.c | 7 +-
drivers/gpu/drm/i915/display/intel_hdcp.c | 2 +-
.../drm/i915/display/intel_modeset_setup.c | 2 +-
drivers/gpu/drm/i915/display/intel_pps.c | 4 +-
drivers/gpu/drm/i915/display/intel_psr.c | 6 +-
drivers/gpu/drm/i915/i915_driver.c | 32 +-
drivers/gpu/drm/xe/display/xe_display.c | 28 +-
15 files changed, 900 insertions(+), 902 deletions(-)
--
2.39.5
next reply other threads:[~2024-11-27 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 17:06 Jani Nikula [this message]
2024-11-27 17:06 ` [PATCH 1/7] drm/i915/display: simplify conditional compilation on runtime PM debug Jani Nikula
2024-11-28 12:31 ` Imre Deak
2024-11-28 12:35 ` Imre Deak
2024-11-28 15:39 ` Jani Nikula
2024-11-27 17:06 ` [PATCH 2/7] drm/i915/display: convert for_each_power_well() to struct intel_display Jani Nikula
2024-11-27 17:06 ` [PATCH 3/7] drm/i915/display: convert for_each_power_domain_well() " Jani Nikula
2024-11-27 17:06 ` [PATCH 4/7] drm/i915/display: convert power wells " Jani Nikula
2024-11-27 17:06 ` [PATCH 5/7] drm/i915/display: convert power domain code internally " Jani Nikula
2024-11-27 17:06 ` [PATCH 6/7] drm/i915/display: convert high level power interfaces " Jani Nikula
2024-11-27 17:06 ` [PATCH 7/7] drm/i915/display: convert power map " Jani Nikula
2024-11-27 17:12 ` ✓ CI.Patch_applied: success for drm/i915/display: power conversion " Patchwork
2024-11-27 17:12 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-27 17:14 ` ✓ CI.KUnit: success " Patchwork
2024-11-27 17:32 ` ✓ CI.Build: " Patchwork
2024-11-27 17:34 ` ✓ CI.Hooks: " Patchwork
2024-11-27 17:35 ` ✗ CI.checksparse: warning " Patchwork
2024-11-27 17:54 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-27 18:58 ` ✗ Xe.CI.Full: failure " 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=cover.1732727056.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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;
as well as URLs for NNTP newsgroup(s).