From: "Heiko Stübner" <heiko@sntech.de>
To: Sandy Huang <hjc@rock-chips.com>,
Andy Yan <andy.yan@rock-chips.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>,
Chaoyi Chen <kernel@airkyi.com>
Cc: dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Chaoyi Chen <chaoyi.chen@rock-chips.com>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH v5 0/3] DSI Controller improvements for Rockchip platforms
Date: Tue, 15 Sep 2026 15:36:47 +0200 [thread overview]
Message-ID: <3800544.yaVYbkx8dN@diego> (raw)
In-Reply-To: <20260914013331.108-1-kernel@airkyi.com>
Hi,
Am Montag, 14. September 2026, 03:33:28 Mitteleuropäische Sommerzeit schrieb Chaoyi Chen:
> From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>
> This series is dedicated to enhancing the DSI controller and PHY timing
> interaction, refining the lane rate calculation, and addressing the
> associated hardware limitations.
Took me a bit to finally test all the different variants for a display
that shows strange behaviour. Sorry this gets a bit longer.
The display in question is the ltk050h3148w [0], display in portrait
orientation.
Ever since commit ac87d23694f4 ("drm/bridge: synopsys: dw-mipi-dsi: Use
pixel clock rate to calculate lbcc") [1] and the subsequent fix in commit
93e82bb4de01 ("drm/bridge: synopsys: dw-mipi-dsi: Fix hcomponent lbcc for
burst mode") [2], that display has its output shifted about 20 pixels to
the right, with the line then continuing on the next display line.
We have this display running on all the Theobroma-System modules, so there
is a lot of variant data :-) .
Your series actually fixed the PX30 part of that shifted output, but for
the RK3399 the results are sort of mixed:
What was confusing me was that in the Rockchip vendor kernel, _all_ DSI
variants use the standard px30 phy settings? The whole original lookup
table seems to be gone? And that replicating that setting actually fixes
the shifted output on RK3399 too?
RK3399:
original:
shifted
mode-clock 59400, target_mbps 450
patches 1+2:
shifted
mode-clock 59400, target_mbps 450
patch 3:
blank disiplay
mode-clock 59400, target_mbps 400
use static px30 phy with patch3:
image is compressed in height and displayed two times one below the other
image is _not_ shifted anymore (so left+right alignment are correct)
mode-clock 59400, target_mbps 400
use static px30 phy without patch3:
image is _not_ shifted anymore
output is correct
mode-clock 59400, target_mbps 450
PX30:
original
shifted
mode-clock 59556, target_mbps 450
patches 1+2:
output is correct
image is _not_ shifted anymore (so left+right alignment are correct)
mode-clock 59556, target_mbps 450
patch 3:
output is still correct
mode-clock 59556, target_mbps 400
RK3588 (DSI2) for reference:
output is correct
mode-clock 59756, lane_mbps 398
Do you have any insight, what could go wrong here?
I'll apply patches 1+2 as they're correct, but will keep patch3 out
for now.
Also Sashiko seems to still be unhappy with patch3.
Thanks a lot
Heiko
[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/panel/panel-leadtek-ltk050h3146w.c#n299
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ac87d23694f44af44a98d21dd77016f2756b6b1b
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=93e82bb4de0196c4caeca1d8a6eef67863981d8f
next prev parent reply other threads:[~2026-09-15 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 1:33 Chaoyi Chen
2026-09-14 1:33 ` [PATCH v5 1/3] drm/rockchip: dsi: Add maximum per lane bit rate calculation Chaoyi Chen
2026-09-14 1:33 ` [PATCH v5 2/3] drm/rockchip: dsi: Add dphy_get_timing support for multiple PHY types Chaoyi Chen
2026-09-14 1:33 ` [PATCH v5 3/3] drm/rockchip: dsi: Relax the lane rate margin requirements Chaoyi Chen
2026-09-15 13:36 ` Heiko Stübner [this message]
2026-09-16 1:54 ` [PATCH v5 0/3] DSI Controller improvements for Rockchip platforms Chaoyi Chen
2026-09-15 16:39 ` (subset) " Heiko Stuebner
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=3800544.yaVYbkx8dN@diego \
--to=heiko@sntech.de \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=chaoyi.chen@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=kernel@airkyi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quentin.schulz@cherry.de \
--cc=simona@ffwll.ch \
--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®