From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 6/6] i915/display/dp: send a more fine-grained link-status uevent
Date: Fri, 15 Oct 2021 22:44:47 +0300 [thread overview]
Message-ID: <YWnaL4WtISzv4msR@intel.com> (raw)
In-Reply-To: <20211015163336.95188-7-contact@emersion.fr>
On Fri, Oct 15, 2021 at 04:33:46PM +0000, Simon Ser wrote:
> 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);
So we're now doing two uevents back to back? Is one not enough?
> }
>
> bool
> --
> 2.33.1
>
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2021-10-15 19:44 UTC|newest]
Thread overview: 25+ 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 ` [PATCH v3 6/6] i915/display/dp: send a more fine-grained link-status uevent Simon Ser
2021-10-15 19:44 ` Ville Syrjälä [this message]
2021-10-18 8:42 ` Simon Ser
2021-10-16 14:03 ` kernel test robot
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=YWnaL4WtISzv4msR@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.