Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <dev@lankhorst.se>
To: intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
	Maarten Lankhorst <dev@lankhorst.se>,
	Matthew Brost <matthew.brost@intel.com>
Subject: [PATCH v2 3/5] drm/xe: Raise gt frequency slightly earlier.
Date: Tue, 21 Jul 2026 16:26:14 +0200	[thread overview]
Message-ID: <20260721142610.93804-10-dev@lankhorst.se> (raw)
In-Reply-To: <20260721142610.93804-7-dev@lankhorst.se>

Move raising the gt frequency to before display_register, so the
blit that's potentially performed to copy stolen memory to system
memory will run at full speed.

Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Maarten Lankhorst <dev@lankhorst.se>
---
 drivers/gpu/drm/xe/xe_device.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
index 4eed9a251e65b..e6c4e1358a614 100644
--- a/drivers/gpu/drm/xe/xe_device.c
+++ b/drivers/gpu/drm/xe/xe_device.c
@@ -1077,6 +1077,9 @@ int xe_device_probe(struct xe_device *xe)
 	if (err)
 		return err;
 
+	for_each_gt(gt, xe, id)
+		xe_gt_sanitize_freq(gt);
+
 	xe_display_register(xe);
 
 	err = xe_oa_register(xe);
@@ -1101,9 +1104,6 @@ int xe_device_probe(struct xe_device *xe)
 	if (err)
 		goto err_unregister_display;
 
-	for_each_gt(gt, xe, id)
-		xe_gt_sanitize_freq(gt);
-
 	xe_vsec_init(xe);
 
 	err = xe_sriov_init_late(xe);
-- 
2.53.0


  parent reply	other threads:[~2026-07-21 14:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 14:26 [PATCH v2 0/5] drm/xe/display: Transparant fallback from stolen to sysmem Maarten Lankhorst
2026-07-21 14:26 ` [PATCH v2 1/5] drm/xe/display: Avoid using stolen memory for framebuffer when media gt exists Maarten Lankhorst
2026-07-22 18:18   ` Shankar, Uma
2026-07-21 14:26 ` [PATCH v2 2/5] drm/xe/migrate: Support copying between sysmem and stolen Maarten Lankhorst
2026-07-21 19:25   ` [PATCH] " Maarten Lankhorst
2026-07-22 19:01     ` Shankar, Uma
2026-07-23 11:21       ` Maarten Lankhorst
2026-07-23 14:00     ` Matthew Auld
2026-07-21 14:26 ` Maarten Lankhorst [this message]
2026-07-21 14:26 ` [PATCH v2 4/5] HACK: Always fallback Maarten Lankhorst
2026-07-21 14:26 ` [PATCH v2 5/5] drm/i915: Introduce intel_bo_fbdev_bios_fb_takeover() Maarten Lankhorst
2026-07-23  9:06   ` Shankar, Uma
2026-07-23 13:37     ` Maarten Lankhorst
2026-07-21 15:27 ` ✓ i915.CI.BAT: success for drm/xe/display: Transparant fallback from stolen to sysmem. (rev2) Patchwork
2026-07-21 20:32 ` ✓ i915.CI.BAT: success for drm/xe/display: Transparant fallback from stolen to sysmem. (rev3) Patchwork
2026-07-22 17:21 ` ✗ i915.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=20260721142610.93804-10-dev@lankhorst.se \
    --to=dev@lankhorst.se \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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