mirror of https://lore.kernel.org/lkml/
 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>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Benjamin Bara <benjamin.bara@skidata.com>,
	Linus Walleij <linusw@kernel.org>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	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>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v8 04/11] arm64: dts: renesas: add support for solidrun rzg2l som and hb-iiot evb
Date: Mon, 28 Sep 2026 14:10:53 +0000	[thread overview]
Message-ID: <133af08e-be3d-4eb5-aa64-63090aef6e97@solid-run.com> (raw)
In-Reply-To: <CAMuHMdUGOLr6TQvfS9i2W1ihBWUUuTG0=TcfyZ-Seb02+XW_3w@mail.gmail.com>

Hi Geert,

Am 23.09.26 um 16:37 schrieb Geert Uytterhoeven:
> On Fri, 4 Sept 2026 at 13:56, Josua Mayer <josua@solid-run.com> wrote:
>> Add support for the SolidRun RZ/G2L SoM [1] on HummingBoard IIoT [2].
>>
>> The SoM features:
>> - 2x 1Gbps Ethernet with PHY
>> - eMMC
>> - 1/2GB DDR
>> - WiFi + Bluetooth
>> - SDHI Mux switching between eMMC and Carrier Board
>>
>> The HummingBoard IIoT features:
>> - 3x USB-2.0 Type A connector
>> - 2x 1Gbps RJ45 Ethernet
>> - USB Type-C Console Port
>> - microSD connector
>> - RTC with backup battery
>> - RGB Status LED
>> - 1x M.2 B-Key connector with USB-2.0 + SIM card holder
>> - 1x DSI Display Connector
>> - GPIO header
>> - 2x RS232/RS485 ports (configurable)
>> - 2x CAN
>>
>> Descriptions for eMMC, microSD and RS485 are provided as overlays due to
>> their dependency on configurable mux states.
>>
>> [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/hummingboard-rz-series-sbcs/hummingboard-rz-g2l-iot-sbc/
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
> Thanks for your patch!
>
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/renesas/rzg2l-hummingboard-iiot-common.dtsi
>> +       aliases {
>> +               gpio1 = &tca6408_u48;
>> +               gpio2 = &tca6408_u37;
>> +               gpio3 = &tca6416_u20;
>> +               gpio4 = &tca6416_u21;
> The TCA64xx driver does not seem to support gpio aliases,
I have confirmed this now. My expectation was that setting gpio aliases
helps make /dev/gpiochip numbering predictable, however this does
not currently work.
> so please
> drop these.
Is this a good reason to drop the aliases, or better to define them 
regardless?
>
>> +               i2c3 = &i2c_exp;
>> +               i2c4 = &i2c_csi;
>> +               i2c5 = &i2c_dsi;
>> +               i2c6 = &i2c_lvds;
>> +               rtc0 = &carrier_rtc;
>> +               rtc1 = &pmic;
>> +               serial3 = &scif3;
>> +       };
>> +       v_1_2: regulator-1-2 {
> Preferred node name is "regulator-1v2"...
Ack, will change with v9, same for rzg2l-hummingboard-pulse-common.dtsi.
>
>> +               compatible = "regulator-fixed";
>> +               regulator-name = "1v2";
>> +               regulator-max-microvolt = <1200000>;
>> +               regulator-min-microvolt = <1200000>;
>> +       };
>> +
>> +       v_3_3: regulator-3-3 {
> ... "regulator-3v3".
Ack, will change with v9.
>
>> +               compatible = "regulator-fixed";
>> +               regulator-name = "3v3";
>> +               regulator-max-microvolt = <3300000>;
>> +               regulator-min-microvolt = <3300000>;
>> +       };
>> +&i2c0 {
>> +       /* highest i2c clock supported by all peripherals is 400kHz */
> We have a DT propery for that ;-)
>
>      clock-frequency = <400000>;
>
> Same for i2c1.

Indeed:

arch/arm64/boot/dts/renesas/rzg2l-sr-som.dtsi-&i2c0 {
arch/arm64/boot/dts/renesas/rzg2l-sr-som.dtsi:clock-frequency = <400000>;
arch/arm64/boot/dts/renesas/rzg2l-sr-som.dtsi-pinctrl-0 = <&i2c0_pins>;

arch/arm64/boot/dts/renesas/rzg2l-sr-som.dtsi-&i2c1 {
arch/arm64/boot/dts/renesas/rzg2l-sr-som.dtsi:clock-frequency = <400000>;
arch/arm64/boot/dts/renesas/rzg2l-sr-som.dtsi-pinctrl-0 = <&i2c1_pins>;

The bus is described in SoM dtsi, where G2LC has an eeprom on i2c0, and
G2L has one on i2c1.

The carrier dtsi then extends each bus with additional devices.
I found it worth restating the conclusive rate in carrier as a comment.

So I will keep clock-frequency in the som dtsi.

>
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/renesas/rzg2l-sr-som.dtsi
>> @@ -0,0 +1,480 @@
>> +// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +/*
>> + * Device Tree Source for the RZ/G2L Solidrun SoM
>> + *
>> + * Copyright 2023 SolidRun Ltd.
>> + * Copyright 2025 Josua Mayer <josua@solid-run.com>
>> + */
>> +
>> +#include <dt-bindings/gpio/gpio.h>
>> +#include <dt-bindings/pinctrl/rzg2l-pinctrl.h>
>> +
>> +/ {
>> +       aliases {
>> +               ethernet0 = &eth0;
>> +               ethernet1 = &eth1;
>> +               gpio0 = &pinctrl;
> The pin control driver does not support gpio aliases, so please
> drop this.
>
>> +               i2c0 = &i2c0;
>> +               i2c1 = &i2c1;
>> +               i2c2 = &i2c3;
>> +               mmc0 = &sdhi0;
>> +               mmc1 = &sdhi1;
>> +               rtc0 = &pmic;
>> +               serial0 = &scif0;
>> +               serial1 = &scif1;
>> +               serial2 = &scif2;
>> +       };
> I didn't compare with the board schematics, but the rest LGTM.

Thanks!


  reply	other threads:[~2026-09-28 14:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 11:56 [PATCH v8 00/11] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards Josua Mayer
2026-09-04 11:56 ` [PATCH v8 01/11] dt-bindings: soc: " Josua Mayer
2026-09-23 13:42   ` Geert Uytterhoeven
2026-09-25  8:28     ` Josua Mayer
2026-09-25  8:36       ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 02/11] dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Allow input-/output-disable Josua Mayer
2026-09-04 12:22   ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 03/11] dt-bindings: usb: cypress,hx3: make peer-hub property optional Josua Mayer
2026-09-04 11:56 ` [PATCH v8 04/11] arm64: dts: renesas: add support for solidrun rzg2l som and hb-iiot evb Josua Mayer
2026-09-23 14:37   ` Geert Uytterhoeven
2026-09-28 14:10     ` Josua Mayer [this message]
2026-09-28 14:31       ` Geert Uytterhoeven
2026-09-28 14:39         ` Josua Mayer
2026-09-04 11:56 ` [PATCH v8 05/11] arm64: dts: renesas: add support for solidrun rzv2l " Josua Mayer
2026-09-23 14:46   ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 06/11] arm64: dts: renesas: add support for solidrun rzg2lc " Josua Mayer
2026-09-23 14:51   ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 07/11] arm64: dts: renesas: rzg2l(c)/rzv2l hb-iiot: add dsi panel dt overlay Josua Mayer
2026-09-23 14:56   ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 08/11] arm64: dts: renesas: add support for solidrun hb-ripple with rzg2l som Josua Mayer
2026-09-23 15:09   ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 09/11] arm64: dts: renesas: add support for solidrun hb-ripple with rzv2l som Josua Mayer
2026-09-23 15:10   ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 10/11] arm64: dts: renesas: add support for solidrun hb-ripple with rzg2lc som Josua Mayer
2026-09-23 15:10   ` Geert Uytterhoeven
2026-09-04 11:56 ` [PATCH v8 11/11] arm64: dts: renesas: add support for solidrun rzg2ul som on hb-ripple Josua Mayer
2026-09-23 15:11   ` Geert Uytterhoeven
2026-09-18 10:08 ` [PATCH v8 00/11] arm64: dts: renesas: Add various SolidRun RZ/G2 based boards 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=133af08e-be3d-4eb5-aa64-63090aef6e97@solid-run.com \
    --to=josua@solid-run.com \
    --cc=benjamin.bara@skidata.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jon@solid-run.com \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mikhail.anikin@solid-run.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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

all inboxes | Powered by JetHome®