public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Josua Mayer <josua@solid-run.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jon Nettleton <jon@solid-run.com>,
	Mikhail Anikin <mikhail.anikin@solid-run.com>,
	Yazan Shhady <yazan.shhady@solid-run.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards
Date: Mon, 4 May 2026 09:38:54 +0000	[thread overview]
Message-ID: <a8e92cd6-690a-4741-a273-6bd7f53222fa@solid-run.com> (raw)
In-Reply-To: <CAMuHMdV=SVDL=7vShMgBas4KyUy7_XWs_9khLZSdggJofsA+VA@mail.gmail.com>

Hi Geert,

Am 04.05.26 um 10:47 schrieb Geert Uytterhoeven:
> Hi Josua,
>
> On Sun, 3 May 2026 at 13:18, Josua Mayer <josua@solid-run.com> wrote:
>> Add support for a variety of oliRun RZ/G2 based SoMs and the
>> HummingBoard IIoT Evaluation board.
>>
>> Bindings are added for all currently known supported boards, namely:
>> - HummingBoard IIoT
>> - HummingBoard Pro
>> - HummingBoard Ripple
>>
>> Device-tree are only added for the first board to reduce effort.
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
> Thanks for your series!
>
> FTR, I found documentation (incl. schematics) at:
>   - RZ/G2L SYSTEM ON MODULE
>     https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-g2l-som/
>   - RZ/V2L SYSTEM ON MODULE
>     https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-v2l-som/#documentation
>   - RZ/G2LC SYSTEM ON MODULE
>     https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-g2lc-som/
>   - RZ/G2UL SYSTEM ON MODULE
>     https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-g2ul-som/
>   - HUMMINGBOARD RZ/G2L IIOT
>     https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/hummingboard-rz-series-sbcs/hummingboard-rz-g2l-iot-sbc/
>   - HUMMINGBOARD RZ/G2L PRO
>     https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/hummingboard-rz-series-sbcs/hummingboard-rz-g2l-sbc/
Should I include these links in future cover letter / or commit descriptions?
>   - HUMMINGBOARD RZ/G2LC BASE
>     https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/hummingboard-rz-series-sbcs/hummingboard-rz-g2lc-base/
>
> I believe "BASE" is the Ripple?

Correct.

Marketing use BASE for product name in combination with G2LC SoM,
however in combination with other SoMs it is known as Ripple.

Compare:

- arch/arm64/boot/dts/freescale/imx8mp-hummingboard-iiot.dts
- arch/arm64/boot/dts/freescale/imx8mp-hummingboard-pro.dts
- arch/arm64/boot/dts/freescale/imx8mp-hummingboard-ripple.dts

To avoid confusion I used the established board name.


regards
Josua Mayer

      reply	other threads:[~2026-05-04  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 11:17 [PATCH 0/4] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards Josua Mayer
2026-05-03 11:17 ` [PATCH 1/4] dt-bindings: soc: " Josua Mayer
2026-05-05 16:42   ` Conor Dooley
2026-05-03 11:17 ` [PATCH 2/4] arm64: dts: renesas: add support for solidrun rzg2l som and hb-iiot evb Josua Mayer
2026-05-03 11:18 ` [PATCH 3/4] arm64: dts: renesas: add support for solidrun rzv2l " Josua Mayer
2026-05-03 11:18 ` [PATCH 4/4] arm64: dts: renesas: add support for solidrun rzg2lc " Josua Mayer
2026-05-04  8:47 ` [PATCH 0/4] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards Geert Uytterhoeven
2026-05-04  9:38   ` Josua Mayer [this message]

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=a8e92cd6-690a-4741-a273-6bd7f53222fa@solid-run.com \
    --to=josua@solid-run.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=jon@solid-run.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mikhail.anikin@solid-run.com \
    --cc=robh@kernel.org \
    --cc=yazan.shhady@solid-run.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox