From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Sharma, Shashank" <shashank.sharma@intel.com>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v3 0/3] Various retries for LSPCON
Date: Fri, 13 Oct 2017 12:19:05 +0300 [thread overview]
Message-ID: <87d15rl81i.fsf@intel.com> (raw)
In-Reply-To: <85fe0ec6-c9b9-5469-26b2-0036aec1a3d2@intel.com>
On Tue, 10 Oct 2017, "Sharma, Shashank" <shashank.sharma@intel.com> wrote:
> Regards
>
> Shashank
>
>
> On 10/10/2017 3:42 PM, Saarinen, Jani wrote:
>> Hi,
>>
>>> -----Original Message-----
>>> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
>>> Of Shashank Sharma
>>> Sent: tiistai 10. lokakuuta 2017 13.08
>>> To: intel-gfx@lists.freedesktop.org
>>> Subject: [Intel-gfx] [PATCH v3 0/3] Various retries for LSPCON
>>>
>>> This patch series adds various retries and delays in DRM and I915 layer, to
>>> handle some of the read failures while dealing with LSPCON devices.
>> Should we have reference to fdo bugs?
>> https://bugs.freedesktop.org/show_bug.cgi?id=102294
>> https://bugs.freedesktop.org/show_bug.cgi?id=102295
> Yes, sure seems like a good idea.
>> and what about this?
>> https://bugs.freedesktop.org/show_bug.cgi?id=102359
> This seems like one probable candidate :)
Pushed the series, thanks for the patches and review. Added a bunch of
likely Bugzilla links to all commits, didn't bother with mapping commits
and bugs. Probably the whole series is needed for most of them anyway.
BR,
Jani.
>
> - Shashank
>>> LSPCON devices are sometimes slow to respond and the vendores expect us
>>> to retry while probing the device.
>>>
>>> The typical scenarios are getting fixed / handled with this patch series are
>>> look like this failure during LSPCON
>>> suspend/resume:
>>> [drm:drm_lspcon_get_mode] *ERROR* LSPCON read(0x80, 0x41) failed
>>> [drm:lspcon_wait_mode [i915]] *ERROR* Error reading LSPCON mode
>>> [drm:drm_lspcon_get_mode] *ERROR* LSPCON read(0x80, 0x41) failed
>>> [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading
>>> LSPCON mode [drm:lspcon_resume [i915]] *ERROR* LSPCON resume failed
>>> Setting dangerous option reset - tainting kernel
>>>
>>> Shashank Sharma (3):
>>> drm: Add retries for lspcon mode detection
>>> drm/i915: Don't give up waiting on INVALID_MODE
>>> drm/i915: Add retries for LSPCON detection
>>>
>>> drivers/gpu/drm/drm_dp_dual_mode_helper.c | 16 +++++++++++++---
>>> drivers/gpu/drm/i915/intel_lspcon.c | 22 +++++++++++++++-------
>>> 2 files changed, 28 insertions(+), 10 deletions(-)
>>>
>>> --
>>> 2.7.4
>>
>> Jani Saarinen
>> Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
>>
>>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-13 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 10:07 [PATCH v3 0/3] Various retries for LSPCON Shashank Sharma
2017-10-10 10:07 ` [PATCH v3 1/3] drm: Add retries for lspcon mode detection Shashank Sharma
2017-10-12 13:42 ` Imre Deak
2017-10-10 10:07 ` [PATCH v3 2/3] drm/i915: Don't give up waiting on INVALID_MODE Shashank Sharma
2017-10-10 10:07 ` [PATCH v3 3/3] drm/i915: Add retries for LSPCON detection Shashank Sharma
2017-10-12 13:47 ` Imre Deak
2017-10-10 10:12 ` [PATCH v3 0/3] Various retries for LSPCON Saarinen, Jani
2017-10-10 11:03 ` Sharma, Shashank
2017-10-13 9:19 ` Jani Nikula [this message]
2017-10-10 10:25 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-10-10 11:46 ` ✓ Fi.CI.IGT: " 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=87d15rl81i.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=shashank.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