From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Add debug print for scaler filter
Date: Fri, 15 Jul 2022 07:44:06 +0000 [thread overview]
Message-ID: <ad04a68cc2954918a7fa2caf7d505445@intel.com> (raw)
In-Reply-To: <20220706102240.21414-1-swati2.sharma@intel.com>
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Swati
> Sharma
> Sent: Wednesday, July 6, 2022 3:53 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH] drm/i915/display: Add debug print for scaler filter
>
> Add debug print statement to print scaler filter property value. Since property can be
> set as either default or integer scaler; its good if we can get debug print for the same
> in dmesg log.
Looks Good to me.
Reviewed-by: Uma Shankar <uma.shankar@intel.com>
> Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_crtc_state_dump.c | 9 +++++----
> drivers/gpu/drm/i915/display/intel_display_debugfs.c | 5 +++--
> 2 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_crtc_state_dump.c
> b/drivers/gpu/drm/i915/display/intel_crtc_state_dump.c
> index 4ca6e9493ff2..e9212f69c360 100644
> --- a/drivers/gpu/drm/i915/display/intel_crtc_state_dump.c
> +++ b/drivers/gpu/drm/i915/display/intel_crtc_state_dump.c
> @@ -134,8 +134,8 @@ static void intel_dump_plane_state(const struct
> intel_plane_state *plane_state)
> plane->base.base.id, plane->base.name,
> fb->base.id, fb->width, fb->height, &fb->format->format,
> fb->modifier, str_yes_no(plane_state->uapi.visible));
> - drm_dbg_kms(&i915->drm, "\trotation: 0x%x, scaler: %d\n",
> - plane_state->hw.rotation, plane_state->scaler_id);
> + drm_dbg_kms(&i915->drm, "\trotation: 0x%x, scaler: %d, scaling_filter:
> %d\n",
> + plane_state->hw.rotation, plane_state->scaler_id,
> +plane_state->hw.scaling_filter);
> if (plane_state->uapi.visible)
> drm_dbg_kms(&i915->drm,
> "\tsrc: " DRM_RECT_FP_FMT " dst: " DRM_RECT_FMT
> "\n", @@ -262,10 +262,11 @@ void intel_crtc_state_dump(const struct
> intel_crtc_state *pipe_config,
>
> if (DISPLAY_VER(i915) >= 9)
> drm_dbg_kms(&i915->drm,
> - "num_scalers: %d, scaler_users: 0x%x, scaler_id: %d\n",
> + "num_scalers: %d, scaler_users: 0x%x, scaler_id: %d,
> +scaling_filter: %d\n",
> crtc->num_scalers,
> pipe_config->scaler_state.scaler_users,
> - pipe_config->scaler_state.scaler_id);
> + pipe_config->scaler_state.scaler_id,
> + pipe_config->hw.scaling_filter);
>
> if (HAS_GMCH(i915))
> drm_dbg_kms(&i915->drm,
> diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> index 6c3954479047..225b6bfc783c 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
> @@ -722,10 +722,11 @@ static void intel_scaler_info(struct seq_file *m, struct
> intel_crtc *crtc)
>
> /* Not all platformas have a scaler */
> if (num_scalers) {
> - seq_printf(m, "\tnum_scalers=%d, scaler_users=%x scaler_id=%d",
> + seq_printf(m, "\tnum_scalers=%d, scaler_users=%x scaler_id=%d
> +scaling_filter=%d",
> num_scalers,
> crtc_state->scaler_state.scaler_users,
> - crtc_state->scaler_state.scaler_id);
> + crtc_state->scaler_state.scaler_id,
> + crtc_state->hw.scaling_filter);
>
> for (i = 0; i < num_scalers; i++) {
> const struct intel_scaler *sc =
> --
> 2.25.1
next prev parent reply other threads:[~2022-07-15 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 10:22 [Intel-gfx] [PATCH] drm/i915/display: Add debug print for scaler filter Swati Sharma
2022-07-06 11:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-07-06 11:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-06 16:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-11 15:01 ` Patchwork
2022-07-11 15:41 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-07-15 7:44 ` Shankar, Uma [this message]
2022-07-19 8:04 ` [Intel-gfx] [PATCH] " Shankar, Uma
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=ad04a68cc2954918a7fa2caf7d505445@intel.com \
--to=uma.shankar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=swati2.sharma@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