From: Pekka Paalanen <ppaalanen@gmail.com>
To: Simon Ser <contact@emersion.fr>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 3/6] drm/connector: use drm_sysfs_connector_hotplug_event
Date: Wed, 27 Oct 2021 16:15:14 +0300 [thread overview]
Message-ID: <20211027161514.431a5851@eldfell> (raw)
In-Reply-To: <20211015163336.95188-4-contact@emersion.fr>
[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]
On Fri, 15 Oct 2021 16:33:43 +0000
Simon Ser <contact@emersion.fr> wrote:
> In drm_connector_register, use drm_sysfs_connector_hotplug_event
> instead of drm_sysfs_hotplug_event, because the hotplug event
> only updates a single connector.
>
> Signed-off-by: Simon Ser <contact@emersion.fr>
> ---
> drivers/gpu/drm/drm_connector.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
> index ec3973e8963c..a50c82bc2b2f 100644
> --- a/drivers/gpu/drm/drm_connector.c
> +++ b/drivers/gpu/drm/drm_connector.c
> @@ -547,7 +547,7 @@ int drm_connector_register(struct drm_connector *connector)
> connector->registration_state = DRM_CONNECTOR_REGISTERED;
>
> /* Let userspace know we have a new connector */
> - drm_sysfs_hotplug_event(connector->dev);
> + drm_sysfs_connector_hotplug_event(connector);
>
> if (connector->privacy_screen)
> drm_privacy_screen_register_notifier(connector->privacy_screen,
Hi Simon,
this might not work for Weston if I understand this right. Kernel is
adding a new connector, which means userspace does not recognise the
connector id in the uevent. Weston as it is right now would ignore the
event rather than add the connector.
The missing piece is for Weston to revert to the old fashioned "recheck
everything" behaviour when hotplug uevent carries anything
unrecognised. Grep for drm_backend_update_conn_props if you want to see
for yourself.
However, I wouldn't NAK this patch just for Weston, but I wonder if
other software would ignore events because of this as well.
A whole another question is, would anyone notice. I guess this can only
be an issue with MST.
All the other changes in this series look fine to me, so them I can give
Acked-by: Pekka Paalanen <pekka.paalanen@collabora.com>
Thanks,
pq
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-27 13:15 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 [this message]
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ä
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=20211027161514.431a5851@eldfell \
--to=ppaalanen@gmail.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.