From: Josua Mayer <josua@solid-run.com>
To: Conor Dooley <conor@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
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 v3 1/4] dt-bindings: soc: renesas: Add various SolidRun RZ/G2 based boards
Date: Wed, 13 May 2026 09:00:04 +0000 [thread overview]
Message-ID: <f2fab17b-fd70-4d83-afee-3809badbb748@solid-run.com> (raw)
In-Reply-To: <20260512-roundup-graveyard-08846d29007e@spud>
Am 12.05.26 um 19:06 schrieb Conor Dooley:
> On Tue, May 12, 2026 at 03:00:05PM +0200, Josua Mayer wrote:
>> Add bindings for various SolidRun boards and System on Module built
>> around Renesas RZ/G2 family of SoCs:
>>
>> - RZ/G2L SoM [1]
>> - RZ/V2L SoM [2]
>> (shares PCB with G2L and has very similar programming model)
>> - RZ/G2LC SoM [3]
>> - RZ/G2UL SoM [4]
>> (shares PCB with G2LC but programming model differs largely)
>> - HummingBoard IIoT [5] (RZ/G2L, RZ/V2L, RZ/G2LC)
>> - HummingBoard Pro [6] (RZ/G2L, RZ/V2L)
>> - HummingBoard Base (Ripple) [7] (RZ/G2L, RZ/V2L, RZ/G2LC, RZ/G2UL)
>>
>> [1] https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-g2l-som/
>> [2] https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-v2l-som/
>> [3] https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-g2lc-som/
>> [4] https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/rz-g2ul-som/
>> [5] https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/hummingboard-rz-series-sbcs/hummingboard-rz-g2l-iot-sbc/
>> [6] https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/hummingboard-rz-series-sbcs/hummingboard-rz-g2l-sbc/
>> [7] https://www.solid-run.com/embedded-industrial-iot/renesas-rz-family/hummingboard-rz-series-sbcs/hummingboard-rz-g2lc-base/
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
> Did I not ack this yesterday?
You did informally, because I forgot to add the Signed-off .....
next prev parent reply other threads:[~2026-05-13 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 13:00 [PATCH v3 0/4] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards Josua Mayer
2026-05-12 13:00 ` [PATCH v3 1/4] dt-bindings: soc: " Josua Mayer
2026-05-12 17:06 ` Conor Dooley
2026-05-13 9:00 ` Josua Mayer [this message]
2026-05-12 13:00 ` [PATCH v3 2/4] arm64: dts: renesas: add support for solidrun rzg2l som and hb-iiot evb Josua Mayer
2026-05-12 13:00 ` [PATCH v3 3/4] arm64: dts: renesas: add support for solidrun rzv2l " Josua Mayer
2026-05-12 13:00 ` [PATCH v3 4/4] arm64: dts: renesas: add support for solidrun rzg2lc " Josua Mayer
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=f2fab17b-fd70-4d83-afee-3809badbb748@solid-run.com \
--to=josua@solid-run.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--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