public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 1/4] drm/i915: Add a notrace version of intel_de_read_fw
Date: Tue, 13 Jun 2023 14:52:42 -0700	[thread overview]
Message-ID: <20230613215245.1551145-2-radhakrishna.sripada@intel.com> (raw)
In-Reply-To: <20230613215245.1551145-1-radhakrishna.sripada@intel.com>

Around the tracing infrastructure, certain registers are being
read resulting in nested traces. Introduce the no trace version
of intel_de_read_fw to be used in such scenarios.

Signed-off-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
---
 drivers/gpu/drm/i915/display/intel_de.h | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/drivers/gpu/drm/i915/display/intel_de.h b/drivers/gpu/drm/i915/display/intel_de.h
index 42552d8c151e..786211121ce2 100644
--- a/drivers/gpu/drm/i915/display/intel_de.h
+++ b/drivers/gpu/drm/i915/display/intel_de.h
@@ -93,6 +93,16 @@ intel_de_wait_for_clear(struct drm_i915_private *i915, i915_reg_t reg,
  * therefore generally be serialised, by either the dev_priv->uncore.lock or
  * a more localised lock guarding all access to that bank of registers.
  */
+static inline u32
+intel_de_read_fw_notrace(struct drm_i915_private *i915, i915_reg_t reg)
+{
+	u32 val;
+
+	val = intel_uncore_read_fw(&i915->uncore, reg);
+
+	return val;
+}
+
 static inline u32
 intel_de_read_fw(struct drm_i915_private *i915, i915_reg_t reg)
 {
-- 
2.34.1


  reply	other threads:[~2023-06-13 21:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 21:52 [Intel-gfx] [PATCH 0/4] Use non traceable api in display trace code Radhakrishna Sripada
2023-06-13 21:52 ` Radhakrishna Sripada [this message]
2023-06-13 21:52 ` [Intel-gfx] [PATCH 2/4] drm/i915: Add a dummy notrace version of intel_de_read64_2x32 Radhakrishna Sripada
2023-06-13 21:52 ` [Intel-gfx] [PATCH 3/4] drm/i915: Make intel_crtc_get_vblank_counter use no trace hw reads Radhakrishna Sripada
2023-06-22 19:41   ` Lucas De Marchi
2023-06-22 21:50     ` Sripada, Radhakrishna
2023-06-13 21:52 ` [Intel-gfx] [PATCH 4/4] drm/i915: Make intel_get_crtc_scanline " Radhakrishna Sripada
2023-06-14  1:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use non traceable api in display trace code Patchwork
2023-06-14  1:04   ` philly j
2023-06-14  1:05   ` philly j
2023-06-14  1:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-14  7:37 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230613215245.1551145-2-radhakrishna.sripada@intel.com \
    --to=radhakrishna.sripada@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