From: Robin van der Gracht <robin.van.der.gracht@protonic.nl>
To: barebox@lists.infradead.org
Cc: Robin van der Gracht <robin.van.der.gracht@protonic.nl>
Subject: [PATCH 0/9] ARM: boards: protonic-mecsbc: Generalization
Date: Wed, 4 Mar 2026 12:00:04 +0100 [thread overview]
Message-ID: <20260304110013.495725-1-robin.van.der.gracht@protonic.nl> (raw)
From: Robin van der Gracht <robin.van.der.gracht@protonic.nl>
Hello,
This patch series makes changes to the existing protonic-mecsbc
board support. These changes pave the way for supporting multiple
simular products with the same board support code. We'll be adding
products with a RK3562 chipset to the mecsbc board code.
For that we'll change the board name to be more generic: protonic-rk356x
Regards,
Robin
David Jander (1):
ARM: boards: protonic-rk356x: Fix crash with different boards
Robin van der Gracht (8):
ARM: boards: Rename protonic-mecsbc to protonic-rk356x
ARM: boards: protonic-rk356x: Remove VIN measurement
ARM: boards: protonic-rk356x: Use devicetree alias for saradc
ARM: boards: protonic-rk356x: Configure ADC and channels in model data
ARM: boards: protonic-rk356x: Move mecsbc code to model init function
ARM: boards: protonic-rk356x: Use rockchip_bbu_mmc_register
ARM: boards: protonic-rk356x: Move bbu setup to device late init
ARM: boards: protonic-rk356x: Read board serial and MAC address from
eMMC
Documentation/boards/rk35xx.rst | 2 +-
arch/arm/boards/Makefile | 2 +-
arch/arm/boards/protonic-mecsbc/board.c | 180 -----------
.../Makefile | 0
arch/arm/boards/protonic-rk356x/board.c | 297 ++++++++++++++++++
.../lowlevel.c | 0
arch/arm/configs/rockchip_v8_defconfig | 2 +-
arch/arm/dts/Makefile | 2 +-
arch/arm/dts/rk3568-mecsbc.dts | 1 +
arch/arm/mach-rockchip/Kconfig | 6 +-
images/Makefile.rockchip | 2 +-
11 files changed, 306 insertions(+), 188 deletions(-)
delete mode 100644 arch/arm/boards/protonic-mecsbc/board.c
rename arch/arm/boards/{protonic-mecsbc => protonic-rk356x}/Makefile (100%)
create mode 100644 arch/arm/boards/protonic-rk356x/board.c
rename arch/arm/boards/{protonic-mecsbc => protonic-rk356x}/lowlevel.c (100%)
--
2.43.0
next reply other threads:[~2026-03-04 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 11:00 Robin van der Gracht [this message]
2026-03-04 11:00 ` [PATCH 1/9] ARM: boards: Rename protonic-mecsbc to protonic-rk356x Robin van der Gracht
2026-03-04 11:00 ` [PATCH 2/9] ARM: boards: protonic-rk356x: Remove VIN measurement Robin van der Gracht
2026-03-04 11:00 ` [PATCH 3/9] ARM: boards: protonic-rk356x: Use devicetree alias for saradc Robin van der Gracht
2026-03-04 11:00 ` [PATCH 4/9] ARM: boards: protonic-rk356x: Configure ADC and channels in model data Robin van der Gracht
2026-03-04 11:00 ` [PATCH 5/9] ARM: boards: protonic-rk356x: Move mecsbc code to model init function Robin van der Gracht
2026-03-04 11:00 ` [PATCH 6/9] ARM: boards: protonic-rk356x: Use rockchip_bbu_mmc_register Robin van der Gracht
2026-03-04 11:00 ` [PATCH 7/9] ARM: boards: protonic-rk356x: Move bbu setup to device late init Robin van der Gracht
2026-03-04 11:00 ` [PATCH 8/9] ARM: boards: protonic-rk356x: Fix crash with different boards Robin van der Gracht
2026-03-04 11:00 ` [PATCH 9/9] ARM: boards: protonic-rk356x: Read board serial and MAC address from eMMC Robin van der Gracht
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=20260304110013.495725-1-robin.van.der.gracht@protonic.nl \
--to=robin.van.der.gracht@protonic.nl \
--cc=barebox@lists.infradead.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