dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Ser <contact@emersion.fr>
To: dri-devel@lists.freedesktop.org
Subject: [PATCH v3 6/6] i915/display/dp: send a more fine-grained link-status uevent
Date: Fri, 15 Oct 2021 16:33:46 +0000	[thread overview]
Message-ID: <20211015163336.95188-7-contact@emersion.fr> (raw)
In-Reply-To: <20211015163336.95188-1-contact@emersion.fr>

When link-status changes, send a hotplug uevent which contains the
connector and property ID. That way, user-space can more easily
figure out that only the link-status property of this connector has
been updated.

Signed-off-by: Simon Ser <contact@emersion.fr>
---
 drivers/gpu/drm/i915/display/intel_dp.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index 04175f359fd6..afbe34b6e5be 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -5264,6 +5264,8 @@ static void intel_dp_modeset_retry_work_fn(struct work_struct *work)
 	mutex_unlock(&connector->dev->mode_config.mutex);
 	/* Send Hotplug uevent so userspace can reprobe */
 	drm_kms_helper_hotplug_event(connector->dev);
+	drm_sysfs_connector_status_event(connector,
+					 connector->dev->mode_config.link_status_property);
 }
 
 bool
-- 
2.33.1



  parent reply	other threads:[~2021-10-15 16:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 16:33 [PATCH v3 0/6] drm: add per-connector hotplug events Simon Ser
2021-10-15 16:33 ` [PATCH v3 1/6] drm/sysfs: introduce drm_sysfs_connector_hotplug_event Simon Ser
2021-10-15 19:37   ` Sam Ravnborg
2021-10-15 19:42     ` Sam Ravnborg
2021-10-15 16:33 ` [PATCH v3 2/6] drm/probe-helper: add drm_kms_helper_connector_hotplug_event Simon Ser
2021-10-15 19:43   ` Sam Ravnborg
2021-10-15 16:33 ` [PATCH v3 3/6] drm/connector: use drm_sysfs_connector_hotplug_event Simon Ser
2021-10-15 19:44   ` Sam Ravnborg
2021-10-27 13:15   ` Pekka Paalanen
2021-10-27 13:26     ` Simon Ser
2021-10-28  7:32       ` Pekka Paalanen
2021-10-15 16:33 ` [PATCH v3 4/6] amdgpu: use drm_kms_helper_connector_hotplug_event Simon Ser
2021-10-15 19:26   ` Harry Wentland
2021-10-15 16:33 ` [PATCH v3 5/6] drm/probe-helper: " Simon Ser
2021-10-15 19:41   ` Ville Syrjälä
2021-10-18  8:43     ` Simon Ser
2021-10-15 20:03   ` Sam Ravnborg
2021-10-18  8:45     ` Simon Ser
2021-10-18  8:15   ` Maxime Ripard
2021-10-18  8:44     ` Simon Ser
2021-10-15 16:33 ` Simon Ser [this message]
2021-10-15 19:44   ` [PATCH v3 6/6] i915/display/dp: send a more fine-grained link-status uevent Ville Syrjälä
2021-10-18  8:42     ` Simon Ser
2021-10-16 14:03   ` kernel test robot

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=20211015163336.95188-7-contact@emersion.fr \
    --to=contact@emersion.fr \
    --cc=dri-devel@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