Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "José Roberto de Souza" <jose.souza@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 2/2] drm/i915/display/drrs: Remove repeated DRRS in i915_drrs_status
Date: Mon, 18 Apr 2022 13:52:21 -0700	[thread overview]
Message-ID: <20220418205221.291891-2-jose.souza@intel.com> (raw)
In-Reply-To: <20220418205221.291891-1-jose.souza@intel.com>

User-space parsing of i915_drrs_status is already broken so lets
use this oportunity to drop those repeated "DRRS".
It is the DRRS status debugfs so all of this information is related to
DRRS and there is no need to mention it each time.

Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
---
 drivers/gpu/drm/i915/display/intel_display_debugfs.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
index 0d7d2e750a4c7..799b0d2bbba18 100644
--- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
+++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
@@ -1074,7 +1074,7 @@ static int intel_drrs_status(struct seq_file *m, struct drm_connector *connector
 	struct drm_i915_private *dev_priv = to_i915(connector->dev);
 	struct intel_crtc *crtc;
 
-	seq_printf(m, "DRRS type: %s\n",
+	seq_printf(m, "Type: %s\n",
 		   intel_drrs_type_str(intel_panel_drrs_type(intel_connector)));
 
 	for_each_intel_crtc(&dev_priv->drm, crtc) {
@@ -1087,16 +1087,16 @@ static int intel_drrs_status(struct seq_file *m, struct drm_connector *connector
 		mutex_lock(&crtc->drrs.mutex);
 
 		/* DRRS Supported */
-		seq_printf(m, "DRRS Enabled: %s\n",
+		seq_printf(m, "Enabled: %s\n",
 			   str_yes_no(crtc_state->has_drrs));
 
-		seq_printf(m, "DRRS Active: %s\n",
+		seq_printf(m, "Active: %s\n",
 			   str_yes_no(intel_drrs_is_active(crtc)));
 
 		seq_printf(m, "Busy_frontbuffer_bits: 0x%X\n",
 			   crtc->drrs.busy_frontbuffer_bits);
 
-		seq_printf(m, "DRRS refresh rate: %s\n",
+		seq_printf(m, "Refresh rate: %s\n",
 			   crtc->drrs.refresh_rate == DRRS_REFRESH_RATE_LOW ?
 			   "low" : "high");
 
-- 
2.35.3


  reply	other threads:[~2022-04-18 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 20:52 [Intel-gfx] [PATCH 1/2] drm/i915/display/drrs: Split the DRRS status per connector José Roberto de Souza
2022-04-18 20:52 ` José Roberto de Souza [this message]
2022-04-18 21:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2022-04-18 23:38 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-21 12:17 ` [Intel-gfx] [PATCH 1/2] " Ville Syrjälä
2022-04-21 13:18   ` Souza, Jose
2022-04-21 13:43     ` Ville Syrjälä

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=20220418205221.291891-2-jose.souza@intel.com \
    --to=jose.souza@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