From: Chaoyi Chen <kernel@airkyi.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonas Karlman <jonas@kwiboo.se>,
Kever Yang <kever.yang@rock-chips.com>,
Jianfeng Liu <liujianfeng1994@gmail.com>,
Dragan Simic <dsimic@manjaro.org>,
Jimmy Hon <honyuenkwun@gmail.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
FUKAUMI Naoki <naoki@radxa.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Alexey Charkov <alchark@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Chaoyi Chen <chaoyi.chen@rock-chips.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Add support for rk3399 industry evaluation board
Date: Sun, 27 Apr 2025 17:42:09 +0800 [thread overview]
Message-ID: <20250427094211.246-1-kernel@airkyi.com> (raw)
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
General feature for rk3399 industry evaluation board:
- Rockchip RK3399
- 4GB LPDDR4
- emmc5.1
- SDIO3.0 compatible TF card
- 1x HDMI2.0a TX
- 1x HDMI1.4b RX with TC358749XBG HDMI to MIPI CSI2 bridge chip
- 1x type-c DisplayPort
- 3x USB3.0 Host
- 1x USB2.0 Host
- 1x Ethernet / USB3.0 to Ethernet
Tested with HDMI/GPU/USB2.0/USB3.0/Ethernet/TF card/emmc.
Chaoyi Chen (2):
dt-bindings: arm: rockchip: Add rk3399 industry evaluation board
arm64: dts: rockchip: Add rk3399-evb-ind board
.../devicetree/bindings/arm/rockchip.yaml | 5 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3399-evb-ind.dts | 222 ++++++++++++++++++
3 files changed, 228 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-evb-ind.dts
--
2.49.0
WARNING: multiple messages have this Message-ID (diff)
From: Chaoyi Chen <kernel@airkyi.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Jianfeng Liu <liujianfeng1994@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Jonas Karlman <jonas@kwiboo.se>,
Jimmy Hon <honyuenkwun@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
FUKAUMI Naoki <naoki@radxa.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Alexey Charkov <alchark@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Chaoyi Chen <chaoyi.chen@rock-chips.com>,
Dragan Simic <dsimic@manjaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add support for rk3399 industry evaluation board
Date: Sun, 27 Apr 2025 17:42:09 +0800 [thread overview]
Message-ID: <20250427094211.246-1-kernel@airkyi.com> (raw)
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
General feature for rk3399 industry evaluation board:
- Rockchip RK3399
- 4GB LPDDR4
- emmc5.1
- SDIO3.0 compatible TF card
- 1x HDMI2.0a TX
- 1x HDMI1.4b RX with TC358749XBG HDMI to MIPI CSI2 bridge chip
- 1x type-c DisplayPort
- 3x USB3.0 Host
- 1x USB2.0 Host
- 1x Ethernet / USB3.0 to Ethernet
Tested with HDMI/GPU/USB2.0/USB3.0/Ethernet/TF card/emmc.
Chaoyi Chen (2):
dt-bindings: arm: rockchip: Add rk3399 industry evaluation board
arm64: dts: rockchip: Add rk3399-evb-ind board
.../devicetree/bindings/arm/rockchip.yaml | 5 +
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3399-evb-ind.dts | 222 ++++++++++++++++++
3 files changed, 228 insertions(+)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-evb-ind.dts
--
2.49.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2025-04-27 9:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 9:42 Chaoyi Chen [this message]
2025-04-27 9:42 ` [PATCH 0/2] Add support for rk3399 industry evaluation board Chaoyi Chen
2025-04-27 9:42 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add " Chaoyi Chen
2025-04-27 9:42 ` Chaoyi Chen
2025-04-30 10:22 ` Krzysztof Kozlowski
2025-04-30 10:22 ` Krzysztof Kozlowski
2025-04-27 9:42 ` [PATCH 2/2] arm64: dts: rockchip: Add rk3399-evb-ind board Chaoyi Chen
2025-04-27 9:42 ` Chaoyi Chen
2025-04-27 20:42 ` Andrew Lunn
2025-04-27 20:42 ` Andrew Lunn
2025-04-28 1:47 ` Chaoyi Chen
2025-04-28 1:47 ` Chaoyi Chen
2025-04-28 12:45 ` Andrew Lunn
2025-04-28 12:45 ` Andrew Lunn
2025-04-29 2:42 ` Chaoyi Chen
2025-04-29 2:42 ` Chaoyi Chen
2025-04-29 12:22 ` Andrew Lunn
2025-04-29 12:22 ` Andrew Lunn
2025-04-30 2:03 ` Chaoyi Chen
2025-04-30 2:03 ` Chaoyi Chen
2025-04-28 8:19 ` Quentin Schulz
2025-04-28 8:19 ` Quentin Schulz
2025-04-28 10:01 ` Chaoyi Chen
2025-04-28 10:01 ` Chaoyi Chen
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=20250427094211.246-1-kernel@airkyi.com \
--to=kernel@airkyi.com \
--cc=alchark@gmail.com \
--cc=chaoyi.chen@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--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=liujianfeng1994@gmail.com \
--cc=naoki@radxa.com \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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.