All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsb: Increase log level if DSB engine gets busy
Date: Fri, 27 Dec 2019 11:04:24 +0530	[thread overview]
Message-ID: <32934a52-c653-ca66-4d3e-346623e224b9@intel.com> (raw)
In-Reply-To: <CAKi4VAJOsg5pashSkEjTd4LrrbZ3ZXwK8ivw1PEfQbBrW5gWKA@mail.gmail.com>

On 27-Dec-19 2:39 AM, Lucas De Marchi wrote:
> On Wed, Dec 25, 2019 at 10:07 AM Swati Sharma <swati2.sharma@intel.com> wrote:
>>
>> Increase the log level if DSB engine gets busy. If dsb engine
>> is busy, it should be an error condition to indicate there might be
>> some difficulty with the hardware.
>>
>> If DSB engine gets busy, load luts will fail and as per current
>> driver design if one instance of DSB engine gets busy, we are not
>> allocating the other instance. So, increase the log level to indicate there
>> could be an issue with driver/hardware.
>>
>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_dsb.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c b/drivers/gpu/drm/i915/display/intel_dsb.c
>> index ada006a690df..6f67b5dfa128 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
>> @@ -52,7 +52,7 @@ static inline bool intel_dsb_enable_engine(struct intel_dsb *dsb)
>>
>>          dsb_ctrl = I915_READ(DSB_CTRL(pipe, dsb->id));
>>          if (DSB_STATUS & dsb_ctrl) {
>> -               DRM_DEBUG_KMS("DSB engine is busy.\n");
>> +               DRM_ERROR("DSB engine is busy.\n");
> 
> are we seeing this? Isn't it a dbg message because in this case we
> would fallback to direct mmio?
We are seeing this issue and is already under debug.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7630/shard-tglb5/igt@kms_available_modes_crc@available_mode_test_crc.html

<7> [303.727858] [drm:intel_dsb_commit [i915]] DSB engine is busy.
<7> [303.727975] [drm:icl_load_luts [i915]] DSB engine is busy.
> 
> Lucas De Marchi
> 
>>                  return false;
>>          }
>>
>> @@ -72,7 +72,7 @@ static inline bool intel_dsb_disable_engine(struct intel_dsb *dsb)
>>
>>          dsb_ctrl = I915_READ(DSB_CTRL(pipe, dsb->id));
>>          if (DSB_STATUS & dsb_ctrl) {
>> -               DRM_DEBUG_KMS("DSB engine is busy.\n");
>> +               DRM_ERROR("DSB engine is busy.\n");
>>                  return false;
>>          }
>>
>> --
>> 2.24.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> 
> 


-- 
~Swati Sharma
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-12-27  5:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 17:55 [Intel-gfx] [PATCH] drm/i915/dsb: Increase log level if DSB engine gets busy Swati Sharma
2019-12-25 18:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2019-12-26 21:09 ` [Intel-gfx] [PATCH] " Lucas De Marchi
2019-12-27  5:34   ` Sharma, Swati2 [this message]
2020-01-07 19:20     ` Lucas De Marchi
2019-12-27 11:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2020-02-07  8:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsb: Increase log level if DSB engine gets busy (rev2) Patchwork
2020-02-10  7:16 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=32934a52-c653-ca66-4d3e-346623e224b9@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=lucas.de.marchi@gmail.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.