From: Dmitriy Filchenko <dmitriy@filchenko.org>
To: joseph.kogut@gmail.com
Cc: conor+dt@kernel.org, derosier@cal-sierra.com,
devicetree@vger.kernel.org, heiko@sntech.de,
honyuenkwun@gmail.com, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh@kernel.org
Subject: [PATCH v5 3/3] arm64: dts: rockchip: Add support for CM5 IO carrier
Date: Fri, 11 Jul 2025 17:09:16 -0600 [thread overview]
Message-ID: <20250711230916.2089410-1-dmitriy@filchenko.org> (raw)
In-Reply-To: <20250617-rk3588s-cm5-io-dts-upstream-v5-3-8d96854a5bbd@gmail.com>
Should `vdd_cpu_lit_s0` and some others be in the SoM device tree instead of the IO board? I see it on page 18 of the schematic https://dl.radxa.com/cm5/v2210/radxa_cm5_v2210_schematic.pdf
Additionally, I am getting the following during boot:
```
[ 38.190604] rockchip-pm-domain fd8d8000.power-management:power-controller: Failed to create device link (0x180) with supplier spi2.0 for /power-management@fd8d8000/power-controller/power-domain@12
```
The device is an RK3588s CM5 on the IO board powered through the barrel jack.
--
Dmitriy
next prev parent reply other threads:[~2025-07-11 23:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 22:11 [PATCH v5 0/3] Add Radxa CM5 module and IO board dts Joseph Kogut
2025-06-17 22:11 ` [PATCH v5 1/3] dt-bindings: arm: rockchip: Add Radxa CM5 IO board Joseph Kogut
2025-06-17 22:12 ` [PATCH v5 2/3] arm64: dts: rockchip: Add rk3588 based Radxa CM5 Joseph Kogut
2025-08-07 11:47 ` FUKAUMI Naoki
2025-08-07 13:26 ` FUKAUMI Naoki
2025-06-17 22:12 ` [PATCH v5 3/3] arm64: dts: rockchip: Add support for CM5 IO carrier Joseph Kogut
2025-06-18 1:59 ` Jimmy Hon
2025-06-18 17:51 ` Joseph Kogut
2025-07-11 23:09 ` Dmitriy Filchenko [this message]
2025-08-07 13:20 ` FUKAUMI Naoki
2025-09-03 8:28 ` [PATCH v5 0/3] Add Radxa CM5 module and IO board dts FUKAUMI Naoki
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=20250711230916.2089410-1-dmitriy@filchenko.org \
--to=dmitriy@filchenko.org \
--cc=conor+dt@kernel.org \
--cc=derosier@cal-sierra.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=joseph.kogut@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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).