From: "Heiko Stübner" <heiko@sntech.de>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
damon.ding@rock-chips.com,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: add RK3588 DP carrier from Theobroma Systems
Date: Mon, 11 Aug 2025 09:19:29 +0200 [thread overview]
Message-ID: <10574731.0AQdONaE2F@diego> (raw)
In-Reply-To: <0582b7bc-e5b2-4b5e-821e-8d2c4301579f@cherry.de>
Am Freitag, 25. Juli 2025, 14:29:12 Mitteleuropäische Sommerzeit schrieb Quentin Schulz:
> Hi Heiko,
>
> On 7/23/25 9:09 PM, Heiko Stuebner wrote:
> > From: Heiko Stuebner <heiko.stuebner@cherry.de>
> >
> > The DisplayPort carrier is a very simple baseboard only providing serial,
> > ethernet and a displayport output.
> >
> > But its main functionality is that it routes the Analogix eDP controller
> > to this DisplayPort output, which allows to test that controller simply
> > by hooking it up to a suitable monitor.
> >
> > The Analogix-DP controller supports eDP 1.3 and DP 1.2, so can drive
> > both eDP displays as well as full DP monitors. It does not support DP+
> > so passive DP-to-HDMI adapters won't work.
> >
>
> I tested this on master (2942242dde896) + v2 of the eDP driver as listed
> in the cover letter, or with v3 of the eDP driver +
> 48f05c3b4b701ae7687fd44d462c88b7ac67e952 and in both cases I have weird
> behaviors.
>
> First, `reboot` is stuck for a very long time before actually rebooting.
> I think you have a stacktrace when you tried yourself, I don't so cannot
> send one.
I tracked this down last week. The hang is easily reproduceable and the
fault of the PCIe SMMU. See
https://lore.kernel.org/all/4400329.mogB4TqSGs@diego/
for the full detail.
TL;DR is, SMMU without users (and thus clocks/power-domains/or whatever)
hangs on reboot.
> Also, I tested on two different DP displays, one has a green tint, the
> other one purple. When trying out other resolutions with modetest, the
> kernel would often crash (no trace, just nothing on console, SSH dead).
> Note that the same HW setup with downstream kernel from
> https://git.theobroma-systems.com/tiger-linux.git/log/?h=linux-6.1-stan-rkr3.2-tiger
> works just fine. I would assume this has nothing to do with this Device
> Tree patch here but rather the eDP patches missing some bits maybe?
>
> @Damon do you have some idea?
>
> The display with green tint is a Iiyama ProLite XU2294HSU and the one
> with the purple tint is a Dell P2319H if that helps.
>
> modetest output: https://paste.debian.net/1387797/.
> modetest output with downstream kernel: https://paste.debian.net/1387798/
>
> The Device Tree looks good to me otherwise.
>
> Cheers,
> Quentin
>
prev parent reply other threads:[~2025-08-11 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 19:09 [PATCH v2 0/2] Add RK3588 Tiger DisplayPort carrier Heiko Stuebner
2025-07-23 19:09 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: add RK3588 DP carrier from Theobroma Systems Heiko Stuebner
2025-07-23 19:09 ` [PATCH v2 2/2] arm64: dts: " Heiko Stuebner
2025-07-25 12:29 ` Quentin Schulz
2025-08-11 7:19 ` Heiko Stübner [this message]
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=10574731.0AQdONaE2F@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=damon.ding@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko.stuebner@cherry.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).