From: Robin van der Gracht <robin@protonic.nl>
To: David Jander <david@protonic.nl>,
Robin van der Gracht <robin.van.der.gracht@protonic.nl>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 0/8] ARM: boards: protonic-mecsbc: Generalization
Date: Thu, 12 Mar 2026 10:50:29 +0100 [thread overview]
Message-ID: <882bdcfa-c09a-43ae-b41f-654e4ded2d2c@protonic.nl> (raw)
In-Reply-To: <20260312092113.1d90fd46@erd003.prtnl>
Hi,
On 3/12/26 09:21, David Jander wrote:
> On Tue, 10 Mar 2026 16:24:25 +0100
> Robin van der Gracht <robin.van.der.gracht@protonic.nl> wrote:
>
>> 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
> Why not protonic-rk35xx or something even more generic? protonic-prtpuk is
> already mainlined and the code is very similar to this branch. IMHO it should
> also be merged. Q4/2026 the RK36xx family is being launched. We don't know yet
> whether it will be sufficiently similar/compatible to warrant a hypothetical
> protonic board to also be added here?
The prtpuk is a rk3576.
I'd like to suggest changing it to protonic-rk35xx now so we can merge
the prtpuk
into this board support later on.
If future rk36xx board support aligns with our current rk35xx board
support than we can
always merge that with new patches in the future.
- Robin
next prev parent reply other threads:[~2026-03-12 9:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 15:24 Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 1/8] ARM: boards: Rename protonic-mecsbc to protonic-rk356x Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 2/8] ARM: boards: protonic-rk356x: Remove VIN measurement Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 3/8] ARM: boards: protonic-rk356x: Use devicetree alias for saradc Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 4/8] ARM: boards: protonic-rk356x: Configure ADC and channels in model data Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 5/8] ARM: boards: protonic-rk356x: Move mecsbc code to model init function Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 6/8] ARM: boards: protonic-rk356x: Use rockchip_bbu_mmc_register Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 7/8] ARM: boards: protonic-rk356x: Move bbu setup to device late init Robin van der Gracht
2026-03-10 15:24 ` [PATCH v2 8/8] ARM: boards: protonic-rk356x: Read board serial and MAC address from eMMC Robin van der Gracht
2026-03-12 8:21 ` [PATCH v2 0/8] ARM: boards: protonic-mecsbc: Generalization David Jander
2026-03-12 9:50 ` Robin van der Gracht [this message]
2026-03-13 14:59 ` Sascha Hauer
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=882bdcfa-c09a-43ae-b41f-654e4ded2d2c@protonic.nl \
--to=robin@protonic.nl \
--cc=barebox@lists.infradead.org \
--cc=david@protonic.nl \
--cc=robin.van.der.gracht@protonic.nl \
/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