All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>,
	"Fredrik Schön" <fredrikschon@gmail.com>,
	intel-gfx@lists.freedesktop.org
Cc: "Fredrik Schön" <fredrik.schon@gmail.com>,
	"Imre Deak" <imre.deak@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/i915: Increase LSPCON timeout
Date: Mon, 20 Aug 2018 14:27:21 +0300	[thread overview]
Message-ID: <87o9dx5ld2.fsf@intel.com> (raw)
In-Reply-To: <c860f332-3e91-0522-984a-e34e30f56022@intel.com>

On Mon, 20 Aug 2018, "Sharma, Shashank" <shashank.sharma@intel.com> wrote:
> On 8/18/2018 1:37 AM, Fredrik Schön wrote:
>
>> 100 ms is not enough time for the LSPCON adapter on Intel NUC devices to
>> settle. This causes dropped display modes at boot or screen reconfiguration.
>> Empirical testing can reproduce the error up to a timeout of 190 ms. Basic
>> boot and stress testing at 200 ms has not (yet) failed.
>>
>> Increase timeout to 400 ms to get some margin of error.
>>
>> Changes from v1:
>> The initial suggestion of 1000 ms was lowered due to concerns about delaying
>> valid timeout cases.
>> Update patch metadata.
>>
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107503
>> Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1570392
>> Fixes: 357c0ae9198a ("drm/i915/lspcon: Wait for expected LSPCON mode to settle")
>> Cc: Shashank Sharma <shashank.sharma@intel.com>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Cc: <stable@vger.kernel.org> # v4.11+
>> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Signed-off-by: Fredrik Schön <fredrik.schon@gmail.com>
>> ---
>>   drivers/gpu/drm/i915/intel_lspcon.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_lspcon.c b/drivers/gpu/drm/i915/intel_lspcon.c
>> index 8ae8f42f430a..6b6758419fb3 100644
>> --- a/drivers/gpu/drm/i915/intel_lspcon.c
>> +++ b/drivers/gpu/drm/i915/intel_lspcon.c
>> @@ -74,7 +74,7 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
>>   	DRM_DEBUG_KMS("Waiting for LSPCON mode %s to settle\n",
>>   		      lspcon_mode_name(mode));
>>   
>> -	wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 100);
>> +	wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
>>   	if (current_mode != mode)
>>   		DRM_ERROR("LSPCON mode hasn't settled\n");
>>   
> Looks good to me
> Reviewed-by: Shashank Sharma <shashank.sharma@intel.com>

Pushed to drm-intel-next-queued, thanks for the patch and review.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center

      reply	other threads:[~2018-08-20 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 20:07 [PATCH v2] drm/i915: Increase LSPCON timeout Fredrik Schön
2018-08-17 20:16 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-08-17 20:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-17 21:22 ` ✓ Fi.CI.IGT: " Patchwork
2018-08-20  7:54 ` [PATCH v2] " Sharma, Shashank
2018-08-20 11:27   ` Jani Nikula [this message]

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=87o9dx5ld2.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=fredrik.schon@gmail.com \
    --cc=fredrikschon@gmail.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shashank.sharma@intel.com \
    --cc=stable@vger.kernel.org \
    /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.