From: "Navare, Manasi" <manasi.d.navare@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915: Dump the crtc hw state always
Date: Tue, 22 Feb 2022 14:38:38 -0800 [thread overview]
Message-ID: <20220222223832.GB22644@labuser-Z97X-UD5H> (raw)
In-Reply-To: <20220217103221.10405-2-ville.syrjala@linux.intel.com>
On Thu, Feb 17, 2022 at 12:32:18PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Let's just dump the "full" hw crtc state in debugs so that we can
> see if some stale junk was left behind when the crtc is supposed
> to be entirely off.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
So basically always print the debugfs even for crtcs that are not enabled to catch any stale state?
Reviewed-by: Manasi Navare <manasi.d.navare@intel.com>
Manasi
> ---
> .../gpu/drm/i915/display/intel_display_debugfs.c | 16 +++++++---------
> 1 file changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index 84be489c3399..f1d78b1c7702 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -923,17 +923,15 @@ 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));
>
> - if (crtc_state->hw.enable) {
> - seq_printf(m, "\thw: active=%s, adjusted_mode=" DRM_MODE_FMT "\n",
> - yesno(crtc_state->hw.active),
> - DRM_MODE_ARG(&crtc_state->hw.adjusted_mode));
> + seq_printf(m, "\thw: active=%s, adjusted_mode=" DRM_MODE_FMT "\n",
> + yesno(crtc_state->hw.active),
> + DRM_MODE_ARG(&crtc_state->hw.adjusted_mode));
>
> - seq_printf(m, "\tpipe src size=%dx%d, dither=%s, bpp=%d\n",
> - crtc_state->pipe_src_w, crtc_state->pipe_src_h,
> - yesno(crtc_state->dither), crtc_state->pipe_bpp);
> + seq_printf(m, "\tpipe src size=%dx%d, dither=%s, bpp=%d\n",
> + crtc_state->pipe_src_w, crtc_state->pipe_src_h,
> + yesno(crtc_state->dither), crtc_state->pipe_bpp);
>
> - intel_scaler_info(m, crtc);
> - }
> + intel_scaler_info(m, crtc);
>
> if (crtc_state->bigjoiner)
> seq_printf(m, "\tLinked to 0x%x pipes as a %s\n",
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-02-22 22:38 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 [this message]
2022-02-17 10:32 ` [Intel-gfx] [PATCH 2/4] drm/i915: Dump hw.enable and pipe_mode Ville Syrjala
2022-02-22 22:41 ` 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=20220222223832.GB22644@labuser-Z97X-UD5H \
--to=manasi.d.navare@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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