From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 6/8] drm/i915/display: move dpll funcs under dpll sub-struct
Date: Thu, 30 Apr 2026 11:28:50 +0300 [thread overview]
Message-ID: <02efd924d7efdf42655f5c9bfd0f79a6df5fe2b4.1777537663.git.jani.nikula@intel.com> (raw)
In-Reply-To: <cover.1777537663.git.jani.nikula@intel.com>
Move dpll related functions under dpll sub-struct of struct
intel_display.
The funcs sub-struct of struct intel_display seems unnecessary. Instead
of display->funcs.FEATURE, prefer display->FEATURE.funcs.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
.../gpu/drm/i915/display/intel_display_core.h | 6 ++--
drivers/gpu/drm/i915/display/intel_dpll.c | 28 +++++++++----------
2 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
index 0c2e17edbd5f..5a1aee340728 100644
--- a/drivers/gpu/drm/i915/display/intel_display_core.h
+++ b/drivers/gpu/drm/i915/display/intel_display_core.h
@@ -127,6 +127,9 @@ struct intel_audio {
* dpll, because on some platforms plls share registers.
*/
struct intel_dpll_global {
+ /* internal dpll functions */
+ const struct intel_dpll_global_funcs *funcs;
+
struct mutex lock;
int num_dpll;
@@ -313,9 +316,6 @@ struct intel_display {
/* Display CDCLK functions */
const struct intel_cdclk_funcs *cdclk;
-
- /* Display pll funcs */
- const struct intel_dpll_global_funcs *dpll;
} funcs;
struct {
diff --git a/drivers/gpu/drm/i915/display/intel_dpll.c b/drivers/gpu/drm/i915/display/intel_dpll.c
index a1aa88598013..f40807a5566b 100644
--- a/drivers/gpu/drm/i915/display/intel_dpll.c
+++ b/drivers/gpu/drm/i915/display/intel_dpll.c
@@ -1735,7 +1735,7 @@ int intel_dpll_crtc_compute_clock(struct intel_atomic_state *state,
if (!crtc_state->hw.enable)
return 0;
- ret = display->funcs.dpll->crtc_compute_clock(state, crtc);
+ ret = display->dpll.funcs->crtc_compute_clock(state, crtc);
if (ret) {
drm_dbg_kms(display->drm, "[CRTC:%d:%s] Couldn't calculate DPLL settings\n",
crtc->base.base.id, crtc->base.name);
@@ -1759,10 +1759,10 @@ int intel_dpll_crtc_get_dpll(struct intel_atomic_state *state,
if (!crtc_state->hw.enable || crtc_state->intel_dpll)
return 0;
- if (!display->funcs.dpll->crtc_get_dpll)
+ if (!display->dpll.funcs->crtc_get_dpll)
return 0;
- ret = display->funcs.dpll->crtc_get_dpll(state, crtc);
+ ret = display->dpll.funcs->crtc_get_dpll(state, crtc);
if (ret) {
drm_dbg_kms(display->drm, "[CRTC:%d:%s] Couldn't get a shared DPLL\n",
crtc->base.base.id, crtc->base.name);
@@ -1776,27 +1776,27 @@ void
intel_dpll_init_clock_hook(struct intel_display *display)
{
if (HAS_LT_PHY(display))
- display->funcs.dpll = &xe3plpd_dpll_funcs;
+ display->dpll.funcs = &xe3plpd_dpll_funcs;
else if (DISPLAY_VER(display) >= 14)
- display->funcs.dpll = &mtl_dpll_funcs;
+ display->dpll.funcs = &mtl_dpll_funcs;
else if (display->platform.dg2)
- display->funcs.dpll = &dg2_dpll_funcs;
+ display->dpll.funcs = &dg2_dpll_funcs;
else if (DISPLAY_VER(display) >= 9 || HAS_DDI(display))
- display->funcs.dpll = &hsw_dpll_funcs;
+ display->dpll.funcs = &hsw_dpll_funcs;
else if (HAS_PCH_SPLIT(display))
- display->funcs.dpll = &ilk_dpll_funcs;
+ display->dpll.funcs = &ilk_dpll_funcs;
else if (display->platform.cherryview)
- display->funcs.dpll = &chv_dpll_funcs;
+ display->dpll.funcs = &chv_dpll_funcs;
else if (display->platform.valleyview)
- display->funcs.dpll = &vlv_dpll_funcs;
+ display->dpll.funcs = &vlv_dpll_funcs;
else if (display->platform.g4x)
- display->funcs.dpll = &g4x_dpll_funcs;
+ display->dpll.funcs = &g4x_dpll_funcs;
else if (display->platform.pineview)
- display->funcs.dpll = &pnv_dpll_funcs;
+ display->dpll.funcs = &pnv_dpll_funcs;
else if (DISPLAY_VER(display) != 2)
- display->funcs.dpll = &i9xx_dpll_funcs;
+ display->dpll.funcs = &i9xx_dpll_funcs;
else
- display->funcs.dpll = &i8xx_dpll_funcs;
+ display->dpll.funcs = &i8xx_dpll_funcs;
}
static bool i9xx_has_pps(struct intel_display *display)
--
2.47.3
next prev parent reply other threads:[~2026-04-30 8:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 8:28 [PATCH 0/8] drm/i915/display: refactor display funcs Jani Nikula
2026-04-30 8:28 ` [PATCH 1/8] drm/i915/display: move audio funcs under audio sub-struct Jani Nikula
2026-04-30 8:28 ` [PATCH 2/8] drm/i915/display: move color funcs under color sub-struct Jani Nikula
2026-04-30 8:28 ` [PATCH 3/8] drm/i915/display: move fdi funcs under fdi sub-struct Jani Nikula
2026-04-30 8:28 ` [PATCH 4/8] drm/i915/display: move watermark funcs under wm sub-struct Jani Nikula
2026-04-30 8:28 ` [PATCH 5/8] drm/i915/display: move hotplug irq funcs under hotplug sub-struct Jani Nikula
2026-04-30 8:28 ` Jani Nikula [this message]
2026-04-30 8:28 ` [PATCH 7/8] drm/i915/display: move cdclk funcs under cdclk sub-struct Jani Nikula
2026-04-30 8:28 ` [PATCH 8/8] drm/i915/display: move display funcs under modeset sub-struct Jani Nikula
2026-04-30 8:36 ` ✓ CI.KUnit: success for drm/i915/display: refactor display funcs Patchwork
2026-04-30 9:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-30 19:38 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-04 6:43 ` [PATCH 0/8] " Garg, Nemesa
2026-05-04 12:34 ` 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=02efd924d7efdf42655f5c9bfd0f79a6df5fe2b4.1777537663.git.jani.nikula@intel.com \
--to=jani.nikula@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