Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
	Matt Atwood <matthew.s.atwood@intel.com>,
	Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH v6 5/9] drm/i915: Set max cdclk for display 30.02
Date: Fri, 13 Jun 2025 15:52:52 +0530	[thread overview]
Message-ID: <20250613102256.3508267-6-dnyaneshwar.bhadane@intel.com> (raw)
In-Reply-To: <20250613102256.3508267-1-dnyaneshwar.bhadane@intel.com>

From: Matt Atwood <matthew.s.atwood@intel.com>

Display version 30.02 has a lower max cdclk rate than 30.00.

Bspec: 68861
Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
---
 drivers/gpu/drm/i915/display/intel_cdclk.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c b/drivers/gpu/drm/i915/display/intel_cdclk.c
index 38b3094b37d7..1cbb1d526fe8 100644
--- a/drivers/gpu/drm/i915/display/intel_cdclk.c
+++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
@@ -3386,7 +3386,9 @@ static int intel_compute_max_dotclk(struct intel_display *display)
  */
 void intel_update_max_cdclk(struct intel_display *display)
 {
-	if (DISPLAY_VER(display) >= 30) {
+	if (DISPLAY_VERx100(display) >= 3002) {
+		display->cdclk.max_cdclk_freq = 480000;
+	} else if (DISPLAY_VER(display) >= 30) {
 		display->cdclk.max_cdclk_freq = 691200;
 	} else if (display->platform.jasperlake || display->platform.elkhartlake) {
 		if (display->cdclk.hw.ref == 24000)
-- 
2.34.1


  parent reply	other threads:[~2025-06-13 10:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 10:22 [PATCH v6 0/9] Add WildCat Lake support Dnyaneshwar Bhadane
2025-06-13 10:22 ` [PATCH v6 1/9] drm/i915/xe3lpd: Add support for display version 30.02 Dnyaneshwar Bhadane
2025-06-13 10:22 ` [PATCH v6 2/9] drm/xe/xe3: Add support for graphics IP version 30.03 Dnyaneshwar Bhadane
2025-06-13 10:22 ` [PATCH v6 3/9] drm/xe/xe3: Add support for media IP version 30.02 Dnyaneshwar Bhadane
2025-06-13 10:22 ` [PATCH v6 4/9] drm/i915/xe3lpd: Update bandwidth parameters for display " Dnyaneshwar Bhadane
2025-06-13 10:22 ` Dnyaneshwar Bhadane [this message]
2025-06-13 10:22 ` [PATCH v6 6/9] drm/xe: Add Wildcat Lake device IDs to PTL list Dnyaneshwar Bhadane
2025-06-13 10:22 ` [PATCH v6 7/9] drm/i915/xe3lpd: Extend DMC load path for display Dnyaneshwar Bhadane
2025-06-13 10:22 ` [PATCH v6 8/9] drm/i915/wcl: C10 phy connected to port A and B Dnyaneshwar Bhadane
2025-06-13 10:22 ` [PATCH v6 9/9] drm/i915/xe3lpd: Extend WA 16023981245 for display 30.02 Dnyaneshwar Bhadane
  -- strict thread matches above, loose matches on Subject: below --
2025-06-13 19:31 [PATCH v6 0/9] Add WildCat Lake support Dnyaneshwar Bhadane
2025-06-13 19:31 ` [PATCH v6 5/9] drm/i915: Set max cdclk for display 30.02 Dnyaneshwar Bhadane

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=20250613102256.3508267-6-dnyaneshwar.bhadane@intel.com \
    --to=dnyaneshwar.bhadane@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=matthew.s.atwood@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