From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Pekka Paalanen <ppaalanen@gmail.com>,
dri-devel@lists.freedesktop.org,
wayland-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/doc: describe PATH format for DP MST
Date: Tue, 24 Oct 2023 16:03:27 +0300 [thread overview]
Message-ID: <ZTfAn2al6lspfQCI@intel.com> (raw)
In-Reply-To: <TJceGIK3ZUXu0BwrhZUQIJhVtnuTayrPRLcg_KGuxE91o9OPfqxduzZljtreq-z48_1FGMy1z6qppi9UleSqx_hIMJ4GK_CCGBPiyRKkCwM=@emersion.fr>
On Tue, Oct 24, 2023 at 09:03:22AM +0000, Simon Ser wrote:
> On Tuesday, October 24th, 2023 at 09:36, Pekka Paalanen <ppaalanen@gmail.com> wrote:
>
> > Are DP MST port numbers guaranteed to be tied to the physical hardware
> > configuration (e.g. how cables are connected) and therefore stable
> > across reboots? What about stable across kernel upgrades?
> >
> > If I knew that, I could perhaps manufacture a stable identifier in
> > userspace by replacing the parent connector ID with a stable connector
> > designator.
>
> Hm, my assumption is that these are stable, but maybe that's also wrong?
> Ville, Dmitry, do you know whether the DP MST port numbers are
> guaranteed stable across reboots when retaining the exact same hardware
> configuration (not the software, maybe the user upgraded the kernel)?
I suspect in practice those should remain the same as long as the
topology didn't change, but I don't think there's anything in the
DP spec that actually guarantees that (eg. some branch device
could in theory reshuffle its port numbers on a whim).
But there is no stable identifier for the corresponding SST
connector anyway so I don't know what you would even do with
stable port numbers.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-10-24 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 20:36 [PATCH] drm/doc: describe PATH format for DP MST Simon Ser
2023-10-23 21:32 ` Dmitry Baryshkov
2023-10-24 7:36 ` Pekka Paalanen
2023-10-24 9:03 ` Simon Ser
2023-10-24 13:03 ` Ville Syrjälä [this message]
2023-10-24 13:12 ` Pekka Paalanen
2023-10-24 13:37 ` Ville Syrjälä
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=ZTfAn2al6lspfQCI@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=contact@emersion.fr \
--cc=daniel.vetter@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ppaalanen@gmail.com \
--cc=wayland-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.