From: Hermes Wu via B4 Relay <devnull+Hermes.wu.ite.com.tw@kernel.org>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
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>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Allen Chen <allen.chen@ite.com.tw>,
Hermes Wu <hermes.wu@ite.com.tw>
Cc: Pet.Weng@ite.com.tw, Kenneth.Hung@ite.com.tw,
treapking@chromium.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Hermes Wu <Hermes.wu@ite.com.tw>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: [PATCH v4 0/4] drm/bridge: it6505: fix DP link traning and improve compatibility
Date: Tue, 23 Sep 2025 14:23:40 +0800 [thread overview]
Message-ID: <20250923-fix-link-training-v4-0-7c18f5d3891e@ite.com.tw> (raw)
IT6505 supports HW auto link training which will write DPCD and check
training status automatically. Some DP device can not pass
HW auto link training and must set link training step by step.
when HW auto link training fail, it may trigger video FIFO error,
and link training process will reset to beginning, and never try
step training method.
Modify training method improve compatibility to these DP devices.
Signed-off-by: Hermes Wu <Hermes.wu@ite.com.tw>
---
Changes in v4:
- squash patch 2/5 and 3/5, which do two different error check in same
palce.
- edit commit message that warp at 70-77 boundary
- Link to v3: https://lore.kernel.org/r/20250401-fix-link-training-v3-0-7f60f2ab7b8c@ite.com.tw
Changes in v3:
- Patch 1/5 : add commit message for detial about changes
- Patch 2/5 : fix lost variable struct device *dev;
- Patch 3/5 : keep changes and remove refactoring
- Patch 5/5 : merge condition "it6505->step_train_only" check form if condiction into for loop.
- Link to v2: https://lore.kernel.org/r/20250326-fix-link-training-v2-0-756c8306f500@ite.com.tw
Changes in v2:
- 1. Split [PATCH 1/3] into 3 commits
- 2. Drop non necessary variable auto_ttrain_retry
- Link to v1: https://lore.kernel.org/all/20250318-fix-link-training-v1-0-19266711142c@ite.com.tw/
---
Hermes Wu (4):
drm/bridge: it6505: fix link training state HW register reset
drm/bridge: it6505: add INT status check while link auto training
drm/bridge: it6505: modify DP link training work
drm/bridge: it6505: skip auto training when previous try fail
drivers/gpu/drm/bridge/ite-it6505.c | 88 +++++++++++++++++++++----------------
1 file changed, 50 insertions(+), 38 deletions(-)
---
base-commit: 938fbb16aba8f7b88e0fdcf56f315a5bbad41aad
change-id: 20250121-fix-link-training-461495494655
Best regards,
--
Hermes Wu <Hermes.wu@ite.com.tw>
next reply other threads:[~2025-09-23 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 6:23 Hermes Wu via B4 Relay [this message]
2025-09-23 6:23 ` [PATCH v4 1/4] drm/bridge: it6505: fix link training state HW register reset Hermes Wu via B4 Relay
2025-09-23 6:23 ` [PATCH v4 2/4] drm/bridge: it6505: add INT status check while link auto training Hermes Wu via B4 Relay
2025-09-23 9:03 ` Dmitry Baryshkov
2025-09-23 6:23 ` [PATCH v4 3/4] drm/bridge: it6505: modify DP link training work Hermes Wu via B4 Relay
2025-09-23 6:23 ` [PATCH v4 4/4] drm/bridge: it6505: skip auto training when previous try fail Hermes Wu via B4 Relay
2025-09-23 9:04 ` 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=20250923-fix-link-training-v4-0-7c18f5d3891e@ite.com.tw \
--to=devnull+hermes.wu.ite.com.tw@kernel.org \
--cc=Kenneth.Hung@ite.com.tw \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Pet.Weng@ite.com.tw \
--cc=airlied@gmail.com \
--cc=allen.chen@ite.com.tw \
--cc=andrzej.hajda@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hermes.wu@ite.com.tw \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=treapking@chromium.org \
--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®