From: Johan Hovold <johan@kernel.org>
To: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
Cc: Dmitry Baryshkov <lumag@kernel.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dmitry.baryshkov@oss.qualcomm.com,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
laurentiu.tudor1@dell.com, abel.vesa@linaro.org
Subject: Re: drm/msm/dp: Introduce link training per-segment for LTTPRs
Date: Mon, 28 Apr 2025 09:45:24 +0200 [thread overview]
Message-ID: <aA8yFI2Bvm-lFJTl@hovoldconsulting.com> (raw)
In-Reply-To: <20250417021349.148911-1-alex.vinarskis@gmail.com>
On Thu, Apr 17, 2025 at 04:10:31AM +0200, Aleksandrs Vinarskis wrote:
> Recently added Initial LTTPR support in msm/dp has configured LTTPR(s)
> to non-transparent mode to enable video output on X1E-based devices
> that come with LTTPR on the motherboards. However, video would not work
> if additional LTTPR(s) are present between sink and source, which is
> the case for USB Type-C docks (eg. Dell WD19TB/WD22TB4), and at least
> some universal Thunderbolt/USB Type-C monitors (eg. Dell U2725QE).
Does this mean that the incomplete LTTPR support in 6.15-rc1 broke
adapters or docks with retimers in transparent mode?
You describe at least one of this patches as a fix but I'm not seeing
any Fixes tags or indication that these need to go into 6.15-rc to fix
a regression.
> Changes in v3:
> - Split 1st patch into 3
> - Simplified handling of max_lttpr_lanes/max_lttpr_rate
> - Moved lttpr_common_caps to msm_dp_link (not msm_dp_panel, as LTTPRs
> are link related, not panel related)
> - Picked Stefan's T-b tag (last patch only, as 1st one is getting split)
> - Droped Abel's R-b tags from 1st patch that got split due to high diff
> - Fixed alignment issues, initialization of variables, debug prints
> - Moved lttpr_count to avoid ugly pointer
> - Link to v2: https://lore.kernel.org/all/20250311234109.136510-1-alex.vinarskis@gmail.com/
I tested v2 due to the dependencies in msm-next and DP altmode still
works on my X13s and T14s (while not using any docks):
Tested-by: Johan Hovold <johan+linaro@kernel.org>
> Aleksandrs Vinarskis (4):
> drm/msm/dp: Fix support of LTTPR initialization
> drm/msm/dp: Account for LTTPRs capabilities
> drm/msm/dp: Prepare for link training per-segment for LTTPRs
> drm/msm/dp: Introduce link training per-segment for LTTPRs
Johan
next prev parent reply other threads:[~2025-04-28 7:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 2:10 drm/msm/dp: Introduce link training per-segment for LTTPRs Aleksandrs Vinarskis
2025-04-17 2:10 ` [PATCH v3 1/4] drm/msm/dp: Fix support of LTTPR initialization Aleksandrs Vinarskis
2025-04-24 21:48 ` Dmitry Baryshkov
2025-04-17 2:10 ` [PATCH v3 2/4] drm/msm/dp: Account for LTTPRs capabilities Aleksandrs Vinarskis
2025-04-25 6:53 ` Abel Vesa
2025-04-25 9:20 ` Dmitry Baryshkov
2025-04-17 2:10 ` [PATCH v3 3/4] drm/msm/dp: Prepare for link training per-segment for LTTPRs Aleksandrs Vinarskis
2025-04-25 6:53 ` Abel Vesa
2025-04-25 19:05 ` Dmitry Baryshkov
2025-04-17 2:10 ` [PATCH v3 4/4] drm/msm/dp: Introduce " Aleksandrs Vinarskis
2025-04-25 19:07 ` Dmitry Baryshkov
2025-04-28 20:07 ` Rob Clark
2025-04-24 21:12 ` Rob Clark
2025-04-24 22:14 ` Dmitry Baryshkov
2025-04-28 7:45 ` Johan Hovold [this message]
2025-04-28 9:06 ` Aleksandrs Vinarskis
2025-04-28 12:47 ` Johan Hovold
2025-04-28 14:17 ` Abel Vesa
2025-04-28 18:23 ` Aleksandrs Vinarskis
2025-04-29 6:52 ` Abel Vesa
2025-04-29 7:29 ` Aleksandrs Vinarskis
2025-04-29 7:23 ` Johan Hovold
2025-04-29 7:50 ` Abel Vesa
2025-04-29 8:03 ` Johan Hovold
2025-04-29 10:57 ` Aleksandrs Vinarskis
2025-04-29 11:31 ` Johan Hovold
2025-04-29 13:07 ` 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=aA8yFI2Bvm-lFJTl@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=airlied@gmail.com \
--cc=alex.vinarskis@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=laurentiu.tudor1@dell.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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