From: Sk Anirban <sk.anirban@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, badal.nilawar@intel.com,
riana.tauro@intel.com, karthik.poosa@intel.com,
raag.jadav@intel.com, soham.purkait@intel.com,
mallesh.koujalagi@intel.com, vinay.belgaumkar@intel.com,
rodrigo.vivi@intel.com, Sk Anirban <sk.anirban@intel.com>
Subject: [PATCH v5 0/2] drm/xe/guc: Remove cached frequency values for GuC SLPC
Date: Wed, 29 Oct 2025 16:50:15 +0530 [thread overview]
Message-ID: <20251029112014.3747915-4-sk.anirban@intel.com> (raw)
This series eliminates cached frequency values that were causing stale
data in GuC SLPC parameter handling. Both RPe and RPa frequencies are
now read live from hardware registers on each request.
Signed-off-by: Sk Anirban <sk.anirban@intel.com>
Sk Anirban (2):
drm/xe/guc: Eliminate RPe caching for SLPC parameter handling
drm/xe/guc: Eliminate RPa frequency caching
drivers/gpu/drm/xe/xe_guc_pc.c | 114 ++++++++++++++-------------
drivers/gpu/drm/xe/xe_guc_pc_types.h | 4 -
2 files changed, 60 insertions(+), 58 deletions(-)
--
2.43.0
next reply other threads:[~2025-10-29 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 11:20 Sk Anirban [this message]
2025-10-29 11:20 ` [PATCH v5 1/2] drm/xe/guc: Eliminate RPe caching for SLPC parameter handling Sk Anirban
2025-10-29 18:04 ` Rodrigo Vivi
2025-10-29 18:35 ` Anirban, Sk
2025-10-29 19:58 ` Vivi, Rodrigo
2025-10-29 20:37 ` Belgaumkar, Vinay
2025-10-30 15:11 ` Anirban, Sk
2025-10-30 15:18 ` Anirban, Sk
2025-10-29 11:20 ` [PATCH v5 2/2] drm/xe/guc: Eliminate RPa frequency caching Sk Anirban
2025-10-29 15:40 ` ✓ CI.KUnit: success for drm/xe/guc: Remove cached frequency values for GuC SLPC Patchwork
2025-10-29 16:28 ` ✓ Xe.CI.BAT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-11-04 10:42 [PATCH v5 0/2] " Sk Anirban
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=20251029112014.3747915-4-sk.anirban@intel.com \
--to=sk.anirban@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=soham.purkait@intel.com \
--cc=vinay.belgaumkar@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