When a link-training attempt fails, emit a uevent to user space that
includes the trigger property, which in this case will be
link-statue=Bad.

This will allow userspace to parse the uevent property and better
understand the reason for the previous display configuration failure.

Cc: Jani Nikula <jani.nik...@linux.intel.com>
Cc: Manasi Navare <navareman...@chromium.org>
Cc: Sean Paul <seanp...@chromium.org>
Signed-off-by: Gil Dekel <gilde...@chromium.org>
---
 drivers/gpu/drm/i915/display/intel_dp.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp.c 
b/drivers/gpu/drm/i915/display/intel_dp.c
index aee3845edd2d..772979f163df 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -42,6 +42,7 @@
 #include <drm/drm_crtc.h>
 #include <drm/drm_edid.h>
 #include <drm/drm_probe_helper.h>
+#include <drm/drm_sysfs.h>

 #include "g4x_dp.h"
 #include "i915_drv.h"
@@ -5604,10 +5605,12 @@ static void intel_dp_modeset_retry_work_fn(struct 
work_struct *work)
 {
        struct intel_connector *intel_connector;
        struct drm_connector *connector;
+       struct drm_property *link_status_property;

        intel_connector = container_of(work, typeof(*intel_connector),
                                       modeset_retry_work);
        connector = &intel_connector->base;
+       link_status_property = connector->dev->mode_config.link_status_property;
        drm_dbg_kms(connector->dev, "[CONNECTOR:%d:%s]\n", connector->base.id,
                    connector->name);

@@ -5620,7 +5623,7 @@ static void intel_dp_modeset_retry_work_fn(struct 
work_struct *work)
                                               DRM_MODE_LINK_STATUS_BAD);
        mutex_unlock(&connector->dev->mode_config.mutex);
        /* Send Hotplug uevent so userspace can reprobe */
-       drm_kms_helper_connector_hotplug_event(connector);
+       drm_sysfs_connector_property_event(connector, link_status_property);
 }

 bool
--
Gil Dekel, Software Engineer, Google / ChromeOS Display and Graphics

Reply via email to