From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Abel Vesa <abel.vesa@linaro.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>,
Danilo Krummrich <dakr@redhat.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Rob Clark <robdclark@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Johan Hovold <johan@kernel.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<nouveau@lists.freedesktop.org>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <linux-arm-msm@vger.kernel.org>,
<freedreno@lists.freedesktop.org>,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH v5 4/4] drm/msm/dp: Add support for LTTPR handling
Date: Mon, 3 Feb 2025 16:32:38 -0800 [thread overview]
Message-ID: <e88c821f-3103-4d16-9605-bb88842e8911@quicinc.com> (raw)
In-Reply-To: <20250203-drm-dp-msm-add-lttpr-transparent-mode-set-v5-4-c865d0e56d6e@linaro.org>
On 2/3/2025 2:57 AM, Abel Vesa wrote:
> Link Training Tunable PHY Repeaters (LTTPRs) are defined in DisplayPort
> 1.4a specification. As the name suggests, these PHY repeaters are
> capable of adjusting their output for link training purposes.
>
> According to the DisplayPort standard, LTTPRs have two operating
> modes:
> - non-transparent - it replies to DPCD LTTPR field specific AUX
> requests, while passes through all other AUX requests
> - transparent - it passes through all AUX requests.
>
> Switching between these two modes is done by the DPTX by issuing
> an AUX write to the DPCD PHY_REPEATER_MODE register.
>
> The msm DP driver is currently lacking any handling of LTTPRs.
> This means that if at least one LTTPR is found between DPTX and DPRX,
> the link training would fail if that LTTPR was not already configured
> in transparent mode.
>
> The section 3.6.6.1 from the DisplayPort v2.0 specification mandates
> that before link training with the LTTPR is started, the DPTX may place
> the LTTPR in non-transparent mode by first switching to transparent mode
> and then to non-transparent mode. This operation seems to be needed only
> on first link training and doesn't need to be done again until device is
> unplugged.
>
> It has been observed on a few X Elite-based platforms which have
> such LTTPRs in their board design that the DPTX needs to follow the
> procedure described above in order for the link training to be successful.
>
> So add support for reading the LTTPR DPCD caps to figure out the number
> of such LTTPRs first. Then, for platforms (or Type-C dongles) that have
> at least one such an LTTPR, set its operation mode to transparent mode
> first and then to non-transparent, just like the mentioned section of
> the specification mandates.
>
> Tested-by: Johan Hovold <johan+linaro@kernel.org>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Reviewed-by: Johan Hovold <johan+linaro@kernel.org>
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> ---
> drivers/gpu/drm/msm/dp/dp_display.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
next prev parent reply other threads:[~2025-02-04 0:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 10:57 [PATCH v5 0/4] drm/dp: Rework LTTPR transparent mode handling and add support to msm driver Abel Vesa
2025-02-03 10:57 ` [PATCH v5 1/4] drm/dp: Add helper to set LTTPRs in transparent mode Abel Vesa
2025-02-03 10:57 ` [PATCH v5 2/4] drm/nouveau/dp: Use the generic helper to control LTTPR " Abel Vesa
2025-02-03 10:57 ` [PATCH v5 3/4] drm/i915/dp: " Abel Vesa
2025-02-05 9:23 ` Kandpal, Suraj
2025-02-03 10:57 ` [PATCH v5 4/4] drm/msm/dp: Add support for LTTPR handling Abel Vesa
2025-02-04 0:32 ` Abhinav Kumar [this message]
2025-02-03 13:48 ` ✓ CI.Patch_applied: success for drm/dp: Rework LTTPR transparent mode handling and add support to msm driver (rev5) Patchwork
2025-02-03 13:48 ` ✓ CI.checkpatch: " Patchwork
2025-02-03 13:49 ` ✓ CI.KUnit: " Patchwork
2025-02-03 14:06 ` ✓ CI.Build: " Patchwork
2025-02-03 14:08 ` ✓ CI.Hooks: " Patchwork
2025-02-03 14:09 ` ✗ CI.checksparse: warning " Patchwork
2025-02-03 14:29 ` [PATCH v5 0/4] drm/dp: Rework LTTPR transparent mode handling and add support to msm driver Dmitry Baryshkov
2025-02-03 14:29 ` ✓ Xe.CI.BAT: success for drm/dp: Rework LTTPR transparent mode handling and add support to msm driver (rev5) Patchwork
2025-02-03 15:28 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-21 19:58 ` [PATCH v5 0/4] drm/dp: Rework LTTPR transparent mode handling and add support to msm driver Dmitry Baryshkov
2025-02-25 11:29 ` Jani Nikula
2025-02-25 17:45 ` Lyude Paul
2025-02-25 16:49 ` 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=e88c821f-3103-4d16-9605-bb88842e8911@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=dakr@redhat.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kherbst@redhat.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=robdclark@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--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