From: Liangbin Lian <jjm2473@gmail.com>
To: Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
Liangbin Lian <jjm2473@gmail.com>, Tom Rini <trini@konsulko.com>,
Joseph Chen <chenjh@rock-chips.com>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
Michal Simek <michal.simek@amd.com>, Peng Fan <peng.fan@nxp.com>,
Jonas Karlman <jonas@kwiboo.se>,
Quentin Schulz <quentin.schulz@cherry.de>,
Johan Jonker <jbx6244@gmail.com>, FUKAUMI Naoki <naoki@radxa.com>
Cc: u-boot@lists.denx.de
Subject: [PATCH 0/1] rockchip: rk3568: Add support for LinkEase EasePi R1
Date: Tue, 12 May 2026 17:15:31 +0800 [thread overview]
Message-ID: <20260512091532.97256-1-jjm2473@gmail.com> (raw)
LinkEase EasePi R1 [1] is a high-performance mini router.
Specification:
- Rockchip RK3568
- 2GB/4GB LPDDR4 RAM
- 16GB on-board eMMC
- 1x M.2 key for 2280 NVMe (PCIe 3.0)
- 1x USB 3.0 Type-A
- 1x USB 2.0 Type-C (for USB flashing)
- 2x 1000 Base-T (native, RTL8211F)
- 2x 2500 Base-T (PCIe, RTL8125B)
- 1x HDMI 2.0 Output
- 12v DC Jack
- 1x Power key connected to PMIC
- 2x LEDs (one static power supplied, one GPIO controlled)
[1] https://doc.linkease.com/zh/guide/easepi-r1/hardware.html
Signed-off-by: Liangbin Lian <jjm2473@gmail.com>
---
Liangbin Lian (1):
rockchip: rk3568: Add support for LinkEase EasePi R1
arch/arm/dts/rk3568-easepi-r1-u-boot.dtsi | 7 ++
board/rockchip/evb_rk3568/MAINTAINERS | 6 ++
configs/easepi-r1-rk3568_defconfig | 82 +++++++++++++++++++++++
doc/board/rockchip/rockchip.rst | 1 +
4 files changed, 96 insertions(+)
create mode 100644 arch/arm/dts/rk3568-easepi-r1-u-boot.dtsi
create mode 100644 configs/easepi-r1-rk3568_defconfig
base-commit: 5732bd0f457b4c671e46574d64d4acb099c0f0a5
--
2.51.0
next reply other threads:[~2026-05-12 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 9:15 Liangbin Lian [this message]
2026-05-12 9:15 ` [PATCH 1/1] rockchip: rk3568: Add support for LinkEase EasePi R1 Liangbin Lian
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=20260512091532.97256-1-jjm2473@gmail.com \
--to=jjm2473@gmail.com \
--cc=chenjh@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=michal.simek@amd.com \
--cc=mkorpershoek@kernel.org \
--cc=naoki@radxa.com \
--cc=peng.fan@nxp.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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