* [PATCH v2] arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins
@ 2026-05-14 21:02 Fabrizio Castro
2026-05-14 21:42 ` sashiko-bot
0 siblings, 1 reply; 3+ messages in thread
From: Fabrizio Castro @ 2026-05-14 21:02 UTC (permalink / raw)
To: Geert Uytterhoeven, Magnus Damm, Rob Herring, Krzysztof Kozlowski,
Conor Dooley
Cc: Fabrizio Castro, linux-renesas-soc, devicetree, linux-kernel,
Biju Das, Lad Prabhakar
The HW user manual for the Renesas RZ/T2H and the RZ/N2H states
that for SDR104, SDR50, and HS200 to work properly the eMMC/SDHI
interface pins have to be configured as specified below:
* SDn_CLK pin - drive strength: Ultra High, slew rate: Fast
* Other SDn_* pins: drive strength: High, slew rate: Fast,
Schmitt trigger: disabled (not applicable to SDn_RST pins).
HS DDR and DDR50 are currently not supported, and for every
other bus mode the eMMC/SDHI interface pins should be configured
as specified below:
* SDn_CLK pin - drive strength: High, slew rate: Fast
* Other SDn_* pins: drive strength: Middle, slew rate: Fast,
Schmitt trigger: disabled (not applicable to SDn_RST pins).
Adjust the pin definitions accordingly.
Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
---
v1->v2:
* Take into account the settings for lower speed modes
.../dts/renesas/rzt2h-n2h-evk-common.dtsi | 147 ++++++++++++++++--
1 file changed, 136 insertions(+), 11 deletions(-)
diff --git a/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi b/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
index f87c2492f414..46f4aaac0478 100644
--- a/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
+++ b/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
@@ -275,12 +275,63 @@ data-pins {
<RZT2H_PORT_PINMUX(12, 7, 0x29)>, /* SD0_DATA5 */
<RZT2H_PORT_PINMUX(13, 0, 0x29)>, /* SD0_DATA6 */
<RZT2H_PORT_PINMUX(13, 1, 0x29)>; /* SD0_DATA7 */
+ drive-strength-microamp = <5000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
};
- ctrl-pins {
- pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>, /* SD0_CLK */
- <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
- <RZT2H_PORT_PINMUX(13, 2, 0x29)>; /* SD0_RST# */
+ clk-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>; /* SD0_CLK */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ };
+
+ cmd-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 1, 0x29)>; /* SD0_CMD */
+ drive-strength-microamp = <5000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+
+ rst-pins {
+ pinmux = <RZT2H_PORT_PINMUX(13, 2, 0x29)>; /* SD0_RST# */
+ drive-strength-microamp = <5000>;
+ slew-rate = <1>;
+ };
+ };
+
+ sdhi0_emmc_pins_uhs: sd0-emmc-group-uhs {
+ data-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 2, 0x29)>, /* SD0_DATA0 */
+ <RZT2H_PORT_PINMUX(12, 3, 0x29)>, /* SD0_DATA1 */
+ <RZT2H_PORT_PINMUX(12, 4, 0x29)>, /* SD0_DATA2 */
+ <RZT2H_PORT_PINMUX(12, 5, 0x29)>, /* SD0_DATA3 */
+ <RZT2H_PORT_PINMUX(12, 6, 0x29)>, /* SD0_DATA4 */
+ <RZT2H_PORT_PINMUX(12, 7, 0x29)>, /* SD0_DATA5 */
+ <RZT2H_PORT_PINMUX(13, 0, 0x29)>, /* SD0_DATA6 */
+ <RZT2H_PORT_PINMUX(13, 1, 0x29)>; /* SD0_DATA7 */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+
+ clk-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>; /* SD0_CLK */
+ drive-strength-microamp = <11800>;
+ slew-rate = <1>;
+ };
+
+ cmd-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 1, 0x29)>; /* SD0_CMD */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+
+ rst-pins {
+ pinmux = <RZT2H_PORT_PINMUX(13, 2, 0x29)>; /* SD0_RST# */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
};
};
@@ -299,12 +350,49 @@ data-pins {
<RZT2H_PORT_PINMUX(12, 3, 0x29)>, /* SD0_DATA1 */
<RZT2H_PORT_PINMUX(12, 4, 0x29)>, /* SD0_DATA2 */
<RZT2H_PORT_PINMUX(12, 5, 0x29)>; /* SD0_DATA3 */
+ drive-strength-microamp = <5000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+
+ clk-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>; /* SD0_CLK */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
};
ctrl-pins {
- pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>, /* SD0_CLK */
- <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
+ pinmux = <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
<RZT2H_PORT_PINMUX(22, 5, 0x29)>; /* SD0_CD */
+ drive-strength-microamp = <5000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+ };
+
+ sdhi0_sd_pins_uhs: sd0-sd-group-uhs {
+ data-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 2, 0x29)>, /* SD0_DATA0 */
+ <RZT2H_PORT_PINMUX(12, 3, 0x29)>, /* SD0_DATA1 */
+ <RZT2H_PORT_PINMUX(12, 4, 0x29)>, /* SD0_DATA2 */
+ <RZT2H_PORT_PINMUX(12, 5, 0x29)>; /* SD0_DATA3 */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+
+ clk-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>; /* SD0_CLK */
+ drive-strength-microamp = <11800>;
+ slew-rate = <1>;
+ };
+
+ ctrl-pins {
+ pinmux = <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
+ <RZT2H_PORT_PINMUX(22, 5, 0x29)>; /* SD0_CD */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
};
};
@@ -323,12 +411,49 @@ data-pins {
<RZT2H_PORT_PINMUX(17, 0, 0x29)>, /* SD1_DATA1 */
<RZT2H_PORT_PINMUX(17, 1, 0x29)>, /* SD1_DATA2 */
<RZT2H_PORT_PINMUX(17, 2, 0x29)>; /* SD1_DATA3 */
+ drive-strength-microamp = <5000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+
+ clk-pins {
+ pinmux = <RZT2H_PORT_PINMUX(16, 5, 0x29)>; /* SD1_CLK */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ };
+
+ ctrl-pins {
+ pinmux = <RZT2H_PORT_PINMUX(16, 6, 0x29)>, /* SD1_CMD */
+ <RZT2H_PORT_PINMUX(17, 4, 0x29)>; /* SD1_CD */
+ drive-strength-microamp = <5000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+ };
+
+ sdhi1_pins_uhs: sd1-group-uhs {
+ data-pins {
+ pinmux = <RZT2H_PORT_PINMUX(16, 7, 0x29)>, /* SD1_DATA0 */
+ <RZT2H_PORT_PINMUX(17, 0, 0x29)>, /* SD1_DATA1 */
+ <RZT2H_PORT_PINMUX(17, 1, 0x29)>, /* SD1_DATA2 */
+ <RZT2H_PORT_PINMUX(17, 2, 0x29)>; /* SD1_DATA3 */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
+ };
+
+ clk-pins {
+ pinmux = <RZT2H_PORT_PINMUX(16, 5, 0x29)>; /* SD1_CLK */
+ drive-strength-microamp = <11800>;
+ slew-rate = <1>;
};
ctrl-pins {
- pinmux = <RZT2H_PORT_PINMUX(16, 5, 0x29)>, /* SD1_CLK */
- <RZT2H_PORT_PINMUX(16, 6, 0x29)>, /* SD1_CMD */
+ pinmux = <RZT2H_PORT_PINMUX(16, 6, 0x29)>, /* SD1_CMD */
<RZT2H_PORT_PINMUX(17, 4, 0x29)>; /* SD1_CD */
+ drive-strength-microamp = <9000>;
+ slew-rate = <1>;
+ input-schmitt-disable;
};
};
};
@@ -342,7 +467,7 @@ &sci0 {
#if SD0_EMMC
&sdhi0 {
pinctrl-0 = <&sdhi0_emmc_pins>;
- pinctrl-1 = <&sdhi0_emmc_pins>;
+ pinctrl-1 = <&sdhi0_emmc_pins_uhs>;
pinctrl-names = "default", "state_uhs";
vmmc-supply = <®_3p3v>;
vqmmc-supply = <®_1p8v>;
@@ -357,7 +482,7 @@ &sdhi0 {
#if SD0_SD
&sdhi0 {
pinctrl-0 = <&sdhi0_sd_pins>;
- pinctrl-1 = <&sdhi0_sd_pins>;
+ pinctrl-1 = <&sdhi0_sd_pins_uhs>;
pinctrl-names = "default", "state_uhs";
vmmc-supply = <®_3p3v>;
vqmmc-supply = <&vqmmc_sdhi0>;
@@ -372,7 +497,7 @@ &sdhi0 {
#if SD1_MICRO_SD
&sdhi1 {
pinctrl-0 = <&sdhi1_pins>;
- pinctrl-1 = <&sdhi1_pins>;
+ pinctrl-1 = <&sdhi1_pins_uhs>;
pinctrl-names = "default", "state_uhs";
vmmc-supply = <®_3p3v>;
vqmmc-supply = <&vccq_sdhi1>;
--
2.34.1
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH v2] arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins
2026-05-14 21:02 [PATCH v2] arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins Fabrizio Castro
@ 2026-05-14 21:42 ` sashiko-bot
2026-05-15 8:54 ` Fabrizio Castro
0 siblings, 1 reply; 3+ messages in thread
From: sashiko-bot @ 2026-05-14 21:42 UTC (permalink / raw)
To: Fabrizio Castro; +Cc: wsa+renesas, devicetree, krzk+dt, robh, conor+dt
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Adding pin configuration properties causes the MMC driver probe to fail because the pinctrl-rzt2h driver lacks pinconf support.
- [Medium] Card Detect (CD) pins are incorrectly grouped with CMD pins, inappropriately applying high-speed settings like 'input-schmitt-disable' to a mechanical switch input.
--
commit 90a6446de76af95b915ef59d0035481394029848
Author: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins
This commit configures the eMMC and SDHI interface pins for the Renesas
RZ/T2H and RZ/N2H EVK. It adds drive strength, slew rate, and Schmitt
trigger settings for various bus modes.
> diff --git a/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi b/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
> index 510399febf295..2b43852257974 100644
> --- a/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
> +++ b/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
> @@ -274,12 +274,63 @@ data-pins {
> <RZT2H_PORT_PINMUX(12, 7, 0x29)>, /* SD0_DATA5 */
> <RZT2H_PORT_PINMUX(13, 0, 0x29)>, /* SD0_DATA6 */
> <RZT2H_PORT_PINMUX(13, 1, 0x29)>; /* SD0_DATA7 */
> + drive-strength-microamp = <5000>;
Does adding these pin configuration properties cause the MMC driver probe to
fail?
It appears the pinctrl-rzt2h driver lacks pinconf support, as its
desc->confops is NULL.
When the MMC driver probes and attempts to select the default pin state,
pinctrl_commit_state() will call pinconf_apply_setting(). Because ops is NULL,
pinconf_apply_setting() logs "missing confops" and returns -EINVAL.
This structurally aborts the state transition, which would cause the eMMC
and SDHI interfaces to become completely unusable.
[ ... ]
> @@ -298,12 +349,49 @@ data-pins {
> <RZT2H_PORT_PINMUX(12, 3, 0x29)>, /* SD0_DATA1 */
> <RZT2H_PORT_PINMUX(12, 4, 0x29)>, /* SD0_DATA2 */
> <RZT2H_PORT_PINMUX(12, 5, 0x29)>; /* SD0_DATA3 */
> + drive-strength-microamp = <5000>;
> + slew-rate = <1>;
> + input-schmitt-disable;
> + };
> +
> + clk-pins {
> + pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>; /* SD0_CLK */
> + drive-strength-microamp = <9000>;
> + slew-rate = <1>;
> };
>
> ctrl-pins {
> - pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>, /* SD0_CLK */
> - <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
> + pinmux = <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
> <RZT2H_PORT_PINMUX(22, 5, 0x29)>; /* SD0_CD */
> + drive-strength-microamp = <5000>;
> + slew-rate = <1>;
> + input-schmitt-disable;
> + };
> + };
Is it safe to apply input-schmitt-disable to the Card Detect (SD0_CD) pin?
The Card Detect pin connects to a mechanical slot switch, which typically
experiences contact bounce during card insertion and removal. Schmitt triggers
are required to provide hysteresis and debounce such signals.
Disabling the Schmitt trigger on the CD pin removes this essential protection,
making the system susceptible to noise and false card detection interrupts.
Furthermore, configuring output properties like drive strength and slew rate
on a pure input pin seems semantically incorrect.
Should the CD pin be isolated into its own cd-pins subnode without these
high-speed properties, analogous to how SD0_RST# was correctly separated in
the eMMC configuration?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260514210220.7616-1-fabrizio.castro.jz@renesas.com?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread* RE: [PATCH v2] arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins
2026-05-14 21:42 ` sashiko-bot
@ 2026-05-15 8:54 ` Fabrizio Castro
0 siblings, 0 replies; 3+ messages in thread
From: Fabrizio Castro @ 2026-05-15 8:54 UTC (permalink / raw)
To: sashiko-reviews@lists.linux.dev
Cc: wsa+renesas, devicetree@vger.kernel.org, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org
> From: sashiko-bot@kernel.org <sashiko-bot@kernel.org>
> Sent: 14 May 2026 22:42
> To: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
> Cc: wsa+renesas <wsa+renesas@sang-engineering.com>; devicetree@vger.kernel.org; krzk+dt@kernel.org;
> robh@kernel.org; conor+dt@kernel.org
> Subject: Re: [PATCH v2] arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins
>
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [High] Adding pin configuration properties causes the MMC driver probe to fail because the pinctrl-
> rzt2h driver lacks pinconf support.
> - [Medium] Card Detect (CD) pins are incorrectly grouped with CMD pins, inappropriately applying high-
> speed settings like 'input-schmitt-disable' to a mechanical switch input.
> --
>
> commit 90a6446de76af95b915ef59d0035481394029848
> Author: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
>
> arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins
>
> This commit configures the eMMC and SDHI interface pins for the Renesas
> RZ/T2H and RZ/N2H EVK. It adds drive strength, slew rate, and Schmitt
> trigger settings for various bus modes.
>
> > diff --git a/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
> b/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
> > index 510399febf295..2b43852257974 100644
> > --- a/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
> > +++ b/arch/arm64/boot/dts/renesas/rzt2h-n2h-evk-common.dtsi
> > @@ -274,12 +274,63 @@ data-pins {
> > <RZT2H_PORT_PINMUX(12, 7, 0x29)>, /* SD0_DATA5 */
> > <RZT2H_PORT_PINMUX(13, 0, 0x29)>, /* SD0_DATA6 */
> > <RZT2H_PORT_PINMUX(13, 1, 0x29)>; /* SD0_DATA7 */
> > + drive-strength-microamp = <5000>;
>
> Does adding these pin configuration properties cause the MMC driver probe to
> fail?
>
> It appears the pinctrl-rzt2h driver lacks pinconf support, as its
> desc->confops is NULL.
Support for it has been via the below series, and it will appear in
v7.1
https://lore.kernel.org/linux-renesas-soc/CA+V-a8sRgOePfrEG2HfMp3XnCYXRay58s9fWjjg8yLjqYFvdnA@mail.gmail.com/T/#u
>
> When the MMC driver probes and attempts to select the default pin state,
> pinctrl_commit_state() will call pinconf_apply_setting(). Because ops is NULL,
> pinconf_apply_setting() logs "missing confops" and returns -EINVAL.
>
> This structurally aborts the state transition, which would cause the eMMC
> and SDHI interfaces to become completely unusable.
>
> [ ... ]
>
> > @@ -298,12 +349,49 @@ data-pins {
> > <RZT2H_PORT_PINMUX(12, 3, 0x29)>, /* SD0_DATA1 */
> > <RZT2H_PORT_PINMUX(12, 4, 0x29)>, /* SD0_DATA2 */
> > <RZT2H_PORT_PINMUX(12, 5, 0x29)>; /* SD0_DATA3 */
> > + drive-strength-microamp = <5000>;
> > + slew-rate = <1>;
> > + input-schmitt-disable;
> > + };
> > +
> > + clk-pins {
> > + pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>; /* SD0_CLK */
> > + drive-strength-microamp = <9000>;
> > + slew-rate = <1>;
> > };
> >
> > ctrl-pins {
> > - pinmux = <RZT2H_PORT_PINMUX(12, 0, 0x29)>, /* SD0_CLK */
> > - <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
> > + pinmux = <RZT2H_PORT_PINMUX(12, 1, 0x29)>, /* SD0_CMD */
> > <RZT2H_PORT_PINMUX(22, 5, 0x29)>; /* SD0_CD */
> > + drive-strength-microamp = <5000>;
> > + slew-rate = <1>;
> > + input-schmitt-disable;
> > + };
> > + };
>
> Is it safe to apply input-schmitt-disable to the Card Detect (SD0_CD) pin?
This is as per HW manual, and no issue was observed during testing so far.
Cheers,
Fab
>
> The Card Detect pin connects to a mechanical slot switch, which typically
> experiences contact bounce during card insertion and removal. Schmitt triggers
> are required to provide hysteresis and debounce such signals.
>
> Disabling the Schmitt trigger on the CD pin removes this essential protection,
> making the system susceptible to noise and false card detection interrupts.
>
> Furthermore, configuring output properties like drive strength and slew rate
> on a pure input pin seems semantically incorrect.
>
> Should the CD pin be isolated into its own cd-pins subnode without these
> high-speed properties, analogous to how SD0_RST# was correctly separated in
> the eMMC configuration?
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260514210220.7616-1-
> fabrizio.castro.jz@renesas.com?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-05-15 8:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-14 21:02 [PATCH v2] arm64: dts: renesas: rzt2h-n2h-evk: Configure eMMC/SDHI pins Fabrizio Castro
2026-05-14 21:42 ` sashiko-bot
2026-05-15 8:54 ` Fabrizio Castro
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.