From: Jani Nikula <jani.nikula@intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, ville.syrjala@linux.intel.com
Subject: Re: [PATCH v4 1/5] drm/i915/vrr: Add crtc_state dump for vrr.vsync params
Date: Wed, 20 Nov 2024 14:50:20 +0200 [thread overview]
Message-ID: <87ttc2133n.fsf@intel.com> (raw)
In-Reply-To: <20241120084948.1834306-2-mitulkumar.ajitkumar.golani@intel.com>
On Wed, 20 Nov 2024, Mitul Golani <mitulkumar.ajitkumar.golani@intel.com> wrote:
> Add crtc_state dump for vrr.vsync_{start/end} params to track the
> state correctly.
>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_crtc_state_dump.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> 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 705ec5ad385c..92dbf2cc150c 100644
> --- a/drivers/gpu/drm/i915/display/intel_crtc_state_dump.c
> +++ b/drivers/gpu/drm/i915/display/intel_crtc_state_dump.c
> @@ -296,11 +296,13 @@ void intel_crtc_state_dump(const struct intel_crtc_state *pipe_config,
> intel_dump_buffer("ELD: ", pipe_config->eld,
> drm_eld_size(pipe_config->eld));
>
> - drm_printf(&p, "vrr: %s, vmin: %d, vmax: %d, pipeline full: %d, guardband: %d flipline: %d, vmin vblank: %d, vmax vblank: %d\n",
> + drm_printf(&p, "vrr: %s, vmin: %d, vmax: %d, pipeline full: %d, guardband: %d flipline: %d, vrr_vsync_start: %d, vrr_vsync_end: %d, vmin vblank: %d, vmax vblank: %d\n",
Please look around you, and follow the patterns.
All the other fields here have spaces instead of underscores.
The whole line is all about VRR, there's no need to duplicate vrr in the
individual fields.
BR,
Jani.
> str_yes_no(pipe_config->vrr.enable),
> pipe_config->vrr.vmin, pipe_config->vrr.vmax,
> pipe_config->vrr.pipeline_full, pipe_config->vrr.guardband,
> pipe_config->vrr.flipline,
> + pipe_config->vrr.vsync_start,
> + pipe_config->vrr.vsync_end,
> intel_vrr_vmin_vblank_start(pipe_config),
> intel_vrr_vmax_vblank_start(pipe_config));
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-20 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 8:49 [PATCH v4 0/5] Add AS_SDP to fastset Mitul Golani
2024-11-20 8:49 ` [PATCH v4 1/5] drm/i915/vrr: Add crtc_state dump for vrr.vsync params Mitul Golani
2024-11-20 12:50 ` Jani Nikula [this message]
2024-11-21 4:38 ` Golani, Mitulkumar Ajitkumar
2024-11-20 8:49 ` [PATCH v4 2/5] drm/i915/vrr: Update vrr.vsync_{start, end} computation Mitul Golani
2024-11-20 12:55 ` Nautiyal, Ankit K
2024-11-21 4:41 ` Golani, Mitulkumar Ajitkumar
2024-11-20 8:49 ` [PATCH v4 3/5] drm/i915/dp: fix the Adaptive sync Operation mode for SDP Mitul Golani
2024-11-20 8:49 ` [PATCH v4 4/5] drm/i915/dp: Compute as_sdp.vtotal based on vrr timings Mitul Golani
2024-11-28 4:34 ` Nautiyal, Ankit K
2024-11-20 8:49 ` [PATCH v4 5/5] drm/i915/dp: Compute as_sdp based on if vrr possible Mitul Golani
2024-11-28 4:39 ` Nautiyal, Ankit K
2024-11-20 9:34 ` ✗ Fi.CI.SPARSE: warning for Add AS_SDP to fastset (rev3) 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=87ttc2133n.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--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