From: "Heiko Stübner" <heiko@sntech.de>
To: Shawn Lin <shawn.lin@rock-chips.com>,
Damon Ding <damon.ding@rock-chips.com>,
Vicente Bergas <vicencb@gmail.com>
Cc: Sandy Huang <hjc@rock-chips.com>,
Andy Yan <andy.yan@rock-chips.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [REGRESSION][BISECTED] No display on rk3399-gru-kevin
Date: Wed, 17 Jun 2026 10:45:54 +0200 [thread overview]
Message-ID: <14488973.RDIVbhacDa@diego> (raw)
In-Reply-To: <CAAMcf8CXfvzvEUyoASmp=6efRDNszyPJuFg0OU63Z7gT+oVQ8A@mail.gmail.com>
Hi Vicente,
Am Mittwoch, 17. Juni 2026, 01:05:27 Mitteleuropäische Sommerzeit schrieb Vicente Bergas:
> Hello,
> there are two issues that result on a black screen on the rk3399-gru-kevin.
>
> The first one is due to:
> c8079f83e0bf312645050c17d9c87deb707369c1
> gpio: rockchip: convert to dynamic GPIO base allocation
can you check that your kernel contains
"gpio: rockchip: Fix GPIO regression after conversion to dynamic base allocation"
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=5cd9c6d332f46d1de8b68117fe2a3f1b08ee80ff
> Reverting this does not fix the problem as there is a second one:
> 51eb548ade20158b4f4f8693a95b1f31a2480e8e
> drm/bridge: analogix_dp: Apply DP helper API drm_dp_channel_eq_ok()
>
> That second one depends on:
> d84b087c7662dd65cd51b228219987c31b1cee02
> drm/bridge: analogix_dp: Apply DP helper APIs to get adjusted voltages
> and pre-emphasises
>
> Reverting all three commits from v7.1 make the display work again.
>
> Please, can this be resolved?
and as Damon wrote, please provide logs, so we can see the actual problem
Thanks
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2026-06-17 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 23:05 [REGRESSION][BISECTED] No display on rk3399-gru-kevin Vicente Bergas
2026-06-17 7:30 ` Damon Ding
2026-06-17 8:45 ` 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=14488973.RDIVbhacDa@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=damon.ding@rock-chips.com \
--cc=hjc@rock-chips.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawn.lin@rock-chips.com \
--cc=vicencb@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.