All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Golani,
	Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: RE: [PATCH] drm/i915/display: clean up DP Adaptive Sync SDP state mismatch logging
Date: Wed, 11 Dec 2024 11:44:00 +0200	[thread overview]
Message-ID: <87v7vqy2ov.fsf@intel.com> (raw)
In-Reply-To: <IA1PR11MB6348052818546C6E313CAD60B23D2@IA1PR11MB6348.namprd11.prod.outlook.com>

On Tue, 10 Dec 2024, "Golani, Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jani
>> Nikula
>> Sent: 05 December 2024 15:01
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>
>> Subject: [PATCH] drm/i915/display: clean up DP Adaptive Sync SDP state
>> mismatch logging
>>
>> Pass the drm_printer from intel_pipe_config_compare(), and use it for
>> logging, along with pipe_config_mismatch(), to simplify and unify.
>>
>> While at it, differentiate the VSC and AS SDP log texts from each other.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/i915/display/intel_display.c | 29 +++++++-------------
>>  1 file changed, 10 insertions(+), 19 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c
>> b/drivers/gpu/drm/i915/display/intel_display.c
>> index 28c1b372cc95..1159f8c3d206 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>> @@ -5216,7 +5216,7 @@ pipe_config_dp_vsc_sdp_mismatch(struct
>> drm_printer *p, bool fastset,
>>                               const struct drm_dp_vsc_sdp *a,
>>                               const struct drm_dp_vsc_sdp *b)
>>  {
>> -     pipe_config_mismatch(p, fastset, crtc, name, "dp sdp");
>> +     pipe_config_mismatch(p, fastset, crtc, name, "dp vsc sdp");
>>
>>       drm_printf(p, "expected:\n");
>>       drm_dp_vsc_sdp_log(p, a);
>> @@ -5225,27 +5225,18 @@ pipe_config_dp_vsc_sdp_mismatch(struct
>> drm_printer *p, bool fastset,  }
>>
>>  static void
>> -pipe_config_dp_as_sdp_mismatch(struct drm_i915_private *i915,
>> -                            bool fastset, const char *name,
>> +pipe_config_dp_as_sdp_mismatch(struct drm_printer *p, bool fastset,
>> +                            const struct intel_crtc *crtc,
>> +                            const char *name,
>>                              const struct drm_dp_as_sdp *a,
>>                              const struct drm_dp_as_sdp *b)  {
>> -     struct drm_printer p;
>> +     pipe_config_mismatch(p, fastset, crtc, name, "dp as sdp");
>>
>> -     if (fastset) {
>> -             p = drm_dbg_printer(&i915->drm, DRM_UT_KMS, NULL);
>> -
>> -             drm_printf(&p, "fastset requirement not met in %s dp
>> sdp\n", name);
>> -     } else {
>> -             p = drm_err_printer(&i915->drm, NULL);
>> -
>> -             drm_printf(&p, "mismatch in %s dp sdp\n", name);
>> -     }
>> -
>> -     drm_printf(&p, "expected:\n");
>> -     drm_dp_as_sdp_log(&p, a);
>> -     drm_printf(&p, "found:\n");
>> -     drm_dp_as_sdp_log(&p, b);
>> +     drm_printf(p, "expected:\n");
>> +     drm_dp_as_sdp_log(p, a);
>> +     drm_printf(p, "found:\n");
>> +     drm_dp_as_sdp_log(p, b);
>
> Reviewed-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>

Thanks for the review, pushed to drm-intel-next.

BR,
Jani.


>>  }
>>
>>  /* Returns the length up to and including the last differing byte */ @@ -
>> 5507,7 +5498,7 @@ intel_pipe_config_compare(const struct intel_crtc_state
>> *current_config,  #define PIPE_CONF_CHECK_DP_AS_SDP(name) do { \
>>       if (!intel_compare_dp_as_sdp(&current_config->infoframes.name, \
>>                                     &pipe_config->infoframes.name)) { \
>> -             pipe_config_dp_as_sdp_mismatch(dev_priv, fastset,
>> __stringify(name), \
>> +             pipe_config_dp_as_sdp_mismatch(&p, fastset, crtc,
>> __stringify(name),
>> +\
>>                                               &current_config-
>> >infoframes.name, \
>>                                               &pipe_config-
>> >infoframes.name); \
>>               ret = false; \
>> --
>> 2.39.5
>

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-12-11  9:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  9:30 [PATCH] drm/i915/display: clean up DP Adaptive Sync SDP state mismatch logging Jani Nikula
2024-12-05  9:35 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-05  9:36 ` ✓ CI.checkpatch: " Patchwork
2024-12-05  9:37 ` ✓ CI.KUnit: " Patchwork
2024-12-05  9:57 ` ✓ CI.Hooks: " Patchwork
2024-12-05 11:04 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-05 11:51 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-05 17:43 ` ✗ i915.CI.BAT: " Patchwork
2024-12-10 12:48 ` [PATCH] " Golani, Mitulkumar Ajitkumar
2024-12-11  9:44   ` Jani Nikula [this message]
2024-12-10 15:28 ` ✓ i915.CI.BAT: success for drm/i915/display: clean up DP Adaptive Sync SDP state mismatch logging (rev2) Patchwork
2024-12-10 17:35 ` ✗ i915.CI.Full: failure " 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=87v7vqy2ov.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mitulkumar.ajitkumar.golani@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.