From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [RFC 0/3] drm/i915/dmc: allocate dmc struct dynamically
Date: Thu, 2 Feb 2023 22:47:45 +0200 [thread overview]
Message-ID: <cover.1675370801.git.jani.nikula@intel.com> (raw)
Allocate the >1k dmc struct dynamically, only for platforms that need
it.
Jani Nikula (3):
drm/i915/power: move dc state members to struct i915_power_domains
drm/i915/dmc: drop "ucode" from function names
drm/i915/dmc: allocate dmc structure dynamically
drivers/gpu/drm/i915/display/intel_display.c | 6 +-
.../gpu/drm/i915/display/intel_display_core.h | 8 +-
.../drm/i915/display/intel_display_power.c | 25 +--
.../drm/i915/display/intel_display_power.h | 4 +
.../i915/display/intel_display_power_well.c | 31 ++--
drivers/gpu/drm/i915/display/intel_dmc.c | 159 ++++++++++++------
drivers/gpu/drm/i915/display/intel_dmc.h | 44 +----
.../drm/i915/display/intel_modeset_setup.c | 1 +
drivers/gpu/drm/i915/display/intel_psr.c | 3 +-
drivers/gpu/drm/i915/i915_driver.c | 6 +-
10 files changed, 164 insertions(+), 123 deletions(-)
--
2.34.1
next reply other threads:[~2023-02-02 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 20:47 Jani Nikula [this message]
2023-02-02 20:47 ` [Intel-gfx] [RFC 1/3] drm/i915/power: move dc state members to struct i915_power_domains Jani Nikula
2023-02-03 20:00 ` Imre Deak
2023-02-06 16:21 ` Jani Nikula
2023-02-06 16:58 ` Imre Deak
2023-02-07 10:05 ` Jani Nikula
2023-02-16 12:47 ` Imre Deak
2023-02-02 20:47 ` [Intel-gfx] [RFC 2/3] drm/i915/dmc: drop "ucode" from function names Jani Nikula
2023-02-02 20:47 ` [Intel-gfx] [RFC 3/3] drm/i915/dmc: allocate dmc structure dynamically Jani Nikula
2023-02-02 21:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/dmc: allocate dmc struct dynamically Patchwork
2023-02-02 21:53 ` [Intel-gfx] ✗ Fi.CI.BAT: 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.1675370801.git.jani.nikula@intel.com \
--to=jani.nikula@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