diff options
| author | Dhinakaran Pandiyan <[email protected]> | 2018-09-27 13:57:30 -0700 |
|---|---|---|
| committer | Dhinakaran Pandiyan <[email protected]> | 2018-09-27 19:32:26 -0700 |
| commit | 9ebd8202393dde9d3678c9ec162c1aa63ba17eac (patch) | |
| tree | 3032b0a41339a3724783b15eac8089a7df9c7f9b /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | a2bf92e8cc16f6bf33bc8053c776630c79ad0325 (diff) | |
drm/i915/dp: Fix link retraining comment in intel_dp_long_pulse()
Comment claims link needs to be retrained because the connected sink raised
a long pulse to indicate link loss. If the sink did so,
intel_dp_hotplug() would have handled link retraining. Looking at the
logs in Bugzilla referenced in commit '3cf71bc9904d ("drm/i915: Re-apply
Perform link quality check, unconditionally during long pulse"")', the
issue is that the sink does not trigger an interrupt. What we want is
->detect() from user space to check link status and retrain. Ville's
review for the original patch also indicates the same root cause. So,
rewrite the comment.
v2: Patch split and rewrote comment.
Cc: Lyude Paul <[email protected]>
Cc: Ville Syrjälä <[email protected]>
Cc: Jani Nikula <[email protected]>
Cc: Rodrigo Vivi <[email protected]>
Cc: Jan-Marek Glogowski <[email protected]>
References: 3cf71bc9904d ("drm/i915: Re-apply "Perform link quality check, unconditionally during long pulse"")
Signed-off-by: Dhinakaran Pandiyan <[email protected]>
Reviewed-by: Ville Syrjälä <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions