From: Jani Nikula <jani.nikula@linux.intel.com>
To: Clint Taylor <clinton.a.taylor@intel.com>,
Imre Deak <imre.deak@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix LSPCON TMDS output buffer enabling from low-power state
Date: Wed, 18 Apr 2018 16:46:17 +0300 [thread overview]
Message-ID: <87a7u0wrti.fsf@intel.com> (raw)
In-Reply-To: <85ef9ff2-d2b7-82e8-a409-f501f999217d@intel.com>
On Mon, 16 Apr 2018, Clint Taylor <clinton.a.taylor@intel.com> wrote:
> On 04/16/2018 08:53 AM, Imre Deak wrote:
>> LSPCON adapters in low-power state may ignore the first I2C write during
>> TMDS output buffer enabling, resulting in a blank screen even with an
>> otherwise enabled pipe. Fix this by reading back and validating the
>> written value a few times.
>>
>> The problem was noticed on GLK machines with an onboard LSPCON adapter
>> after entering/exiting DC5 power state. Doing an I2C read of the adapter
>> ID as the first transaction - instead of the I2C write to enable the
>> TMDS buffers - returns the correct value. Based on this we assume that
>> the transaction itself is sent properly, it's only the adapter that is
>> not ready for some reason to accept this first write after waking from
>> low-power state. In my case the second I2C write attempt always
>> succeeded.
>>
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105854
>> Cc: Clinton Taylor <clinton.a.taylor@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Imre Deak <imre.deak@intel.com>
>> ---
>> drivers/gpu/drm/drm_dp_dual_mode_helper.c | 39 +++++++++++++++++++++++++------
>> 1 file changed, 32 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_dp_dual_mode_helper.c b/drivers/gpu/drm/drm_dp_dual_mode_helper.c
>> index 02a50929af67..e7f4fe2848a5 100644
>> --- a/drivers/gpu/drm/drm_dp_dual_mode_helper.c
>> +++ b/drivers/gpu/drm/drm_dp_dual_mode_helper.c
>> @@ -350,19 +350,44 @@ int drm_dp_dual_mode_set_tmds_output(enum drm_dp_dual_mode_type type,
>> {
>> uint8_t tmds_oen = enable ? 0 : DP_DUAL_MODE_TMDS_DISABLE;
>> ssize_t ret;
>> + int retry;
>>
>> if (type < DRM_DP_DUAL_MODE_TYPE2_DVI)
>> return 0;
>>
>> - ret = drm_dp_dual_mode_write(adapter, DP_DUAL_MODE_TMDS_OEN,
>> - &tmds_oen, sizeof(tmds_oen));
>> - if (ret) {
>> - DRM_DEBUG_KMS("Failed to %s TMDS output buffers\n",
>> - enable ? "enable" : "disable");
>> - return ret;
>> + /*
>> + * LSPCON adapters in low-power state may ignore the first write, so
>> + * read back and verify the written value a few times.
>> + */
>> + for (retry = 0; retry < 3; retry++) {
>> + uint8_t tmp;
>> +
>> + ret = drm_dp_dual_mode_write(adapter, DP_DUAL_MODE_TMDS_OEN,
>> + &tmds_oen, sizeof(tmds_oen));
>> + if (ret) {
>> + DRM_DEBUG_KMS("Failed to %s TMDS output buffers (%d attempts)\n",
>> + enable ? "enable" : "disable",
>> + retry + 1);
>> + return ret;
>> + }
>> +
>> + ret = drm_dp_dual_mode_read(adapter, DP_DUAL_MODE_TMDS_OEN,
>> + &tmp, sizeof(tmp));
>> + if (ret) {
>> + DRM_DEBUG_KMS("I2C read failed during TMDS output buffer %s (%d attempts)\n",
>> + enable ? "enabling" : "disabling",
>> + retry + 1);
>> + return ret;
>> + }
>> +
>> + if (tmp == tmds_oen)
>> + return 0;
>> }
>>
>> - return 0;
>> + DRM_DEBUG_KMS("I2C write value mismatch during TMDS output buffer %s\n",
>> + enable ? "enabling" : "disabling");
>> +
>> + return -EIO;
>> }
>> EXPORT_SYMBOL(drm_dp_dual_mode_set_tmds_output);
>>
>
> Appears to fix the issue seen on GLK with LSPCON and DMC firmware
> loaded. Customer was concerned about the fix being in DRM instead of
> i915. However, there are no other SOCs that use this DRM function.
>
> Reviewed-by: Clint Taylor <Clinton.A.Taylor@intel.com>
> Tested-by: Clint Taylor <Clinton.A.Taylor@intel.com>
Pushed to drm-misc-fixes, thanks for the patch.
Clint and Ville, many thanks for your testing and review, alas I screwed
up and pushed this without the tags added to the commit. I'm sorry. I
expect better from myself. :(
BR,
Jani.
>
> -Clint
>
>
> _______________________________________________
> 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:[~2018-04-18 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 15:53 [PATCH] drm/i915: Fix LSPCON TMDS output buffer enabling from low-power state Imre Deak
2018-04-16 17:43 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-04-16 20:44 ` ✓ Fi.CI.IGT: " Patchwork
2018-04-17 0:14 ` [PATCH] " Clint Taylor
2018-04-18 13:46 ` Jani Nikula [this message]
2018-04-17 17:57 ` Ville Syrjälä
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=87a7u0wrti.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=clinton.a.taylor@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).