From: "Heiko Stübner" <heiko@sntech.de>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: shawn.lin@rock-chips.com, linux-rockchip@lists.infradead.org,
"finley.xiao" <finley.xiao@rock-chips.com>,
Detlev Casanova <detlev.casanova@collabora.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [REGRESSION] rk3588s-evb1-v10 board unable to boot based on linux-next
Date: Thu, 12 Feb 2026 14:20:59 +0100 [thread overview]
Message-ID: <3639831.IFkqi6BYcA@diego> (raw)
In-Reply-To: <97daffa1-8767-5eaa-dc03-57e7d817c095@rock-chips.com>
Hi Shawn,
Am Donnerstag, 12. Februar 2026, 14:09:13 Mitteleuropäische Normalzeit schrieb Shawn Lin:
> 在 2026/02/12 星期四 18:48, Heiko Stübner 写道:
> > Am Donnerstag, 12. Februar 2026, 11:35:14 Mitteleuropäische Normalzeit schrieb Shawn Lin:
> >> + Sebastian Reichel
> >>
> >> 在 2026/02/12 星期四 15:59, Shawn Lin 写道:
> >>> Hi Detlev,
> >>>
> >>> commit f61731bd6062 ("arm64: dts: rockchip: Add the vdpu381 Video
> >>> Decoders on RK3588") landed on linux-next breaks rk3588s-evb1-v10.
> >>> Revert it fixes the problem. The full log could be found here[1].
> >>> Also confirm that it doesn't work based on Linus' latest mainline
> >>> as this commit merged into it this cycle.
> >>>
> >>> If anything I could do to help debug it, please let me know.
> >>>
> >>
> >> I did some quick debug and found it's related to a pmdomain patch.
> >> Commit f61731bd6062 happened to enable rkvdec which relys on the
> >> PD_VDEC*, so I have sent a fix patch for you to help review:
> >>
> >> https://lore.kernel.org/linux-rockchip/1770891364-52147-1-git-send-email-shawn.lin@rock-chips.com/T/#u
> >
> > do you want to provide a patch for the evb1 board to that adds the
> > domain-supplies, so that people can see what is needed to make
> > the vdec work?
> >
>
> I do have a plan to add it for evb1 board. Btw,IIRC, peripheral IP
> should be kept as disalbed in soc level dtsi, and then set enabled in
> individual board dts. But rkvdec stuffs in rk3588-base.dtsi seems to
> be an exception?
There is a difference between peripherals _on_ the board, vs. peripherals
that exists _only_ inside the SoC.
Like we keep the sdmmc disabled if there is no card-slot/card on the board.
The video decoders/encoders/etc are only ever inside the SoC with no
relation to the board design itself, so they are _always_ available.
Boards just need to configure the supply relation properly.
With your patch for the pm-domain, we'll make sure, the vdec will not probe
if the board-devicetree is set up wrongly and missing the supply declaration.
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2026-02-12 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 7:59 [REGRESSION] rk3588s-evb1-v10 board unable to boot based on linux-next Shawn Lin
2026-02-12 10:35 ` Shawn Lin
2026-02-12 10:48 ` Heiko Stübner
2026-02-12 13:09 ` Shawn Lin
2026-02-12 13:20 ` 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=3639831.IFkqi6BYcA@diego \
--to=heiko@sntech.de \
--cc=detlev.casanova@collabora.com \
--cc=finley.xiao@rock-chips.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.lin@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox