From: Marius Vlad <marius.vlad@collabora.com>
To: Ian Forbes <ian.forbes@broadcom.com>
Cc: dri-devel@lists.freedesktop.org, daniel.stone@collabora.com,
dmitry.baryshkov@oss.qualcomm.com, jani.nikula@linux.intel.com,
tzimmermann@suse.de, simona.vetter@ffwll.ch,
derek.foreman@collabora.com
Subject: Re: [PATCH 1/2] drm: Introduce a new connector status
Date: Mon, 3 Nov 2025 20:01:12 +0200 [thread overview]
Message-ID: <aQjt6FMINYk9LrfX@xpredator> (raw)
In-Reply-To: <CAO6MGtj8T-ZHASj4xAr=yA-Y+jwsXZ7ErjrQ0FxaVV9Vp+-EFA@mail.gmail.com>
Hi Ian,
On Tue, Sep 23, 2025 at 12:34:58PM -0500, Ian Forbes wrote:
> On Tue, Sep 23, 2025 at 3:36 AM Marius Vlad <marius.vlad@collabora.com> wrote:
> >
> > This patch introduces a new boolean variable used to track connector's
> > connect/disconnect status and it is being used on both polling and
> > the HPD (Hot Plug Detect) paths.
> >
> > A subsequent patch would make use of this connector status to propagate
> > per-connector udev hot plug events. This allows user-space to receive
> > the connector's ID, rather than having a generic hot-plug event for all
> > connectors, or in the HPD path, just the first one found with a
> > connection status change.
> >
> > Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
> > ---
>
> How do you see this working with virtual connectors which can hotplug
> without a connected -> disconnected -> connected cycle?
tbh I don't see how those hot plug events are generated on virtual
connectors. Do you have a particular driver in mind, or how do you
"simulate" that hotplug cycle?
Pushed today a v4 of this patches series which adds polling in the vkms
driver and with that in I'm able to use sysfs and simulate a hot plug
event, like you'd have regular connectors. I've CC'ed on that v4 if
you'd like to have another go.
next prev parent reply other threads:[~2025-11-03 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 8:36 [PATCH v3 0/2] Pass down hot plug CONNECTOR ID to user-space Marius Vlad
2025-09-23 8:36 ` [PATCH 1/2] drm: Introduce a new connector status Marius Vlad
2025-09-23 15:53 ` Dmitry Baryshkov
2025-11-03 18:07 ` Marius Vlad
2025-09-23 17:34 ` Ian Forbes
2025-11-03 18:01 ` Marius Vlad [this message]
2025-09-25 6:51 ` kernel test robot
2025-09-23 8:36 ` [PATCH 2/2] drm: Propagate connector status change Marius Vlad
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=aQjt6FMINYk9LrfX@xpredator \
--to=marius.vlad@collabora.com \
--cc=daniel.stone@collabora.com \
--cc=derek.foreman@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ian.forbes@broadcom.com \
--cc=jani.nikula@linux.intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=tzimmermann@suse.de \
/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