From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Simon Ser <contact@emersion.fr>
Cc: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Janne Grunau" <j@jannau.net>, "Robert Foss" <rfoss@kernel.org>,
"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Andy Gross" <agross@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Jonas Karlman" <jonas@kwiboo.se>, "Leo Li" <sunpeng.li@amd.com>,
intel-gfx@lists.freedesktop.org,
"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
linux-kernel@vger.kernel.org,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 3/4] drm/uapi: document the USB subconnector type
Date: Fri, 18 Aug 2023 13:30:56 +0300 [thread overview]
Message-ID: <6097eb1d-6b00-4a0f-a91f-5b19f2b422eb@linaro.org> (raw)
In-Reply-To: <gIjbz8oq8AuY8E5_XGKnJNjIyQK9SDxp2-3Ep-Dr3D9T_-iUIt-q-oFgarZor4jtdI3682ZtuvQnaQBhTrc5OR6G2sqvDxbmxGZmcRrBAio=@emersion.fr>
On 18/08/2023 09:24, Simon Ser wrote:
> On Thursday, August 17th, 2023 at 21:33, Dmitry Baryshkov <dmitry.baryshkov@linaro.org> wrote:
>
>> We have been looking for a way to document that the corresponding DP
>> port is represented by the USB connector on the device.
>>
>> Consequently, I believe the best way to document it, would be to use
>> DisplayPort / USB, when there is no dongle connected, switching to
>> DisplayPort / HDMI, DisplayPort / VGA, DisplayPort / DisplayPort, etc.
>> when the actual dongle / display is connected and then switching back to
>> the DisplayPort / USB when it gets disconnected.
>>
>> If this sounds good to all parties, I'll post v2, adding this
>> explanation to the cover letter.
>
> But how can user-space discover that the port is USB-C when it's
> connected? That information is lost at this point.
Yes, unfortunately.
> (In addition, this clashes with the existing semantics of the
> subconnector prop as discussed before: USB-C is not sub-, it's super-.)
Ok. How do we proceed then? Is it fine to add another property for DP
case? Do you have any particular property name in mind? I will follow
with addition of this property then.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-08-18 10:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 0:49 [PATCH 0/4] drm/bridge-connector: simplify handling of USB-C DP Dmitry Baryshkov
2023-07-29 0:49 ` [PATCH 1/4] drm: allow specifying default subtype for the DP subconnector property Dmitry Baryshkov
2023-08-02 18:54 ` Laurent Pinchart
2023-08-02 19:01 ` Dmitry Baryshkov
2023-07-29 0:49 ` [PATCH 2/4] drm/bridge-connector: handle subconnector types Dmitry Baryshkov
2023-08-02 8:35 ` Neil Armstrong
2023-08-02 9:05 ` Dmitry Baryshkov
2023-08-02 18:46 ` Laurent Pinchart
2023-08-02 18:51 ` Dmitry Baryshkov
2023-07-29 0:49 ` [PATCH 3/4] drm/uapi: document the USB subconnector type Dmitry Baryshkov
2023-08-02 18:55 ` Laurent Pinchart
2023-08-02 19:01 ` Dmitry Baryshkov
2023-08-02 19:13 ` Laurent Pinchart
2023-08-02 19:23 ` Dmitry Baryshkov
2023-08-03 15:22 ` Simon Ser
2023-08-03 15:31 ` Simon Ser
2023-08-03 15:36 ` Dmitry Baryshkov
2023-08-03 15:43 ` Simon Ser
2023-08-03 15:49 ` Dmitry Baryshkov
2023-08-03 20:44 ` Laurent Pinchart
2023-08-03 20:46 ` Simon Ser
2023-08-03 20:57 ` Dmitry Baryshkov
2023-08-17 19:33 ` Dmitry Baryshkov
2023-08-18 6:24 ` Simon Ser
2023-08-18 10:30 ` Dmitry Baryshkov [this message]
2023-07-29 0:49 ` [PATCH 4/4] soc: qcom: pmic_glink: properly describe the DP connector Dmitry Baryshkov
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=6097eb1d-6b00-4a0f-a91f-5b19f2b422eb@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=agross@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andersson@kernel.org \
--cc=andrzej.hajda@intel.com \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=j@jannau.net \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=konrad.dybcio@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sunpeng.li@amd.com \
--cc=tvrtko.ursulin@linux.intel.com \
--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
all inboxes | Powered by JetHome®