From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 2/4] drm/i915: Dump hw.enable and pipe_mode
Date: Thu, 17 Feb 2022 12:32:19 +0200 [thread overview]
Message-ID: <20220217103221.10405-3-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20220217103221.10405-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Include hw.enable and pipe_mode in the crtc debugfs state dump.
These are fairly fundemental to the operation of the driver
so not seeing them leaves us in the dark.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
drivers/gpu/drm/i915/display/intel_display_debugfs.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
index f1d78b1c7702..1740f24446bb 100644
--- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
+++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
@@ -923,9 +923,12 @@ static void intel_crtc_info(struct seq_file *m, struct intel_crtc *crtc)
yesno(crtc_state->uapi.active),
DRM_MODE_ARG(&crtc_state->uapi.mode));
- seq_printf(m, "\thw: active=%s, adjusted_mode=" DRM_MODE_FMT "\n",
- yesno(crtc_state->hw.active),
+ seq_printf(m, "\thw: enable=%s, active=%s\n",
+ yesno(crtc_state->hw.enable), yesno(crtc_state->hw.active));
+ seq_printf(m, "\tadjusted_mode=" DRM_MODE_FMT "\n",
DRM_MODE_ARG(&crtc_state->hw.adjusted_mode));
+ seq_printf(m, "\tpipe__mode=" DRM_MODE_FMT "\n",
+ DRM_MODE_ARG(&crtc_state->hw.pipe_mode));
seq_printf(m, "\tpipe src size=%dx%d, dither=%s, bpp=%d\n",
crtc_state->pipe_src_w, crtc_state->pipe_src_h,
--
2.34.1
next prev parent reply other threads:[~2022-02-17 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 10:32 [Intel-gfx] [PATCH 0/4] drm/i915: Fix disabled crtc state clearing, again Ville Syrjala
2022-02-17 10:32 ` [Intel-gfx] [PATCH 1/4] drm/i915: Dump the crtc hw state always Ville Syrjala
2022-02-22 22:38 ` Navare, Manasi
2022-02-17 10:32 ` Ville Syrjala [this message]
2022-02-22 22:41 ` [Intel-gfx] [PATCH 2/4] drm/i915: Dump hw.enable and pipe_mode Navare, Manasi
2022-02-22 22:54 ` Navare, Manasi
2022-02-17 10:32 ` [Intel-gfx] [PATCH 3/4] drm/i915: Remove odd any_ms=true assignment Ville Syrjala
2022-02-22 22:50 ` Navare, Manasi
2022-02-17 10:32 ` [Intel-gfx] [PATCH 4/4] drm/i915: Properly clear crtc state when disabling it fully, again Ville Syrjala
2022-02-22 23:00 ` Navare, Manasi
2022-02-17 20:55 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix disabled crtc state clearing, again Patchwork
2022-02-18 7:22 ` [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=20220217103221.10405-3-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.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