From: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
To: David Lechner <dlechner@baylibre.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Sean Wang <sean.wang@mediatek.com>
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 3/4] arm64: dts: mediatek: add device-tree for Genio 720-EVK board
Date: Fri, 20 Mar 2026 13:37:33 +0100 [thread overview]
Message-ID: <7d1e52c0b9c3a6d30e9db617b9bcfa23ed9046b5.camel@collabora.com> (raw)
In-Reply-To: <c2618423-2466-47bb-a8cf-7c849e7e231e@baylibre.com>
Hi David,
On Thu, 2026-03-12 at 19:26 -0500, David Lechner wrote:
> On 12/3/25 7:59 AM, Louis-Alexis Eyraud wrote:
> > Add support for MediaTek MT8189 SoC and its variants, and a device-
> > tree
> > for the basic hardware enablement of the Genio 720-EVK board, based
> > on
> > MT8391 SoC.
> >
>
> ...
>
> > + mmc0_default_pins: mmc0-default-pins {
> > + pins-clk {
> > + pinmux = <PINMUX_GPIO162__FUNC_MSDC0_CLK>;
> > + drive-strength = <6>;
> > + bias-pull-down = <MTK_PUPD_SET_R1R0_10>;
> > + };
> > +
> > + pins-cmd-dat {
> > + pinmux =
> > <PINMUX_GPIO166__FUNC_MSDC0_DAT0>,
> > +
> > <PINMUX_GPIO165__FUNC_MSDC0_DAT1>,
> > +
> > <PINMUX_GPIO164__FUNC_MSDC0_DAT2>,
> > +
> > <PINMUX_GPIO163__FUNC_MSDC0_DAT3>,
> > +
> > <PINMUX_GPIO159__FUNC_MSDC0_DAT4>,
> > +
> > <PINMUX_GPIO158__FUNC_MSDC0_DAT5>,
> > +
> > <PINMUX_GPIO157__FUNC_MSDC0_DAT6>,
> > +
> > <PINMUX_GPIO156__FUNC_MSDC0_DAT7>,
> > + <PINMUX_GPIO161__FUNC_MSDC0_CMD>;
> > + input-enable;
> > + drive-strength = <6>;
> > + bias-pull-up = <MTK_PUPD_SET_R1R0_01>;
> > + };
>
> Should we also have pins-ds here to match mmc0-uhs-pins?
>
The data strobe pin is only used for the HS modes, that is why it is
only declared for uhs state.
No other mediatek board devicetrees have it for default state too, so I
don't think it is needed here.
> > +
> > + pins-rst {
> > + pinmux =
> > <PINMUX_GPIO160__FUNC_MSDC0_RSTB>;
> > + drive-strength = <6>;
> > + bias-pull-up = <MTK_PUPD_SET_R1R0_00>;
> > + };
> > + };
> > +
> > + mmc0_uhs_pins: mmc0-uhs-pins {
> > + pins-clk {
> > + pinmux = <PINMUX_GPIO162__FUNC_MSDC0_CLK>;
> > + drive-strength = <8>;
> > + bias-pull-down = <MTK_PUPD_SET_R1R0_10>;
> > + };
> > +
> > + pins-cmd-dat {
> > + pinmux =
> > <PINMUX_GPIO166__FUNC_MSDC0_DAT0>,
> > +
> > <PINMUX_GPIO165__FUNC_MSDC0_DAT1>,
> > +
> > <PINMUX_GPIO164__FUNC_MSDC0_DAT2>,
> > +
> > <PINMUX_GPIO163__FUNC_MSDC0_DAT3>,
> > +
> > <PINMUX_GPIO159__FUNC_MSDC0_DAT4>,
> > +
> > <PINMUX_GPIO158__FUNC_MSDC0_DAT5>,
> > +
> > <PINMUX_GPIO157__FUNC_MSDC0_DAT6>,
> > +
> > <PINMUX_GPIO156__FUNC_MSDC0_DAT7>,
> > + <PINMUX_GPIO161__FUNC_MSDC0_CMD>;
> > + input-enable;
> > + drive-strength = <8>;
> > + bias-pull-up = <MTK_PUPD_SET_R1R0_01>;
> > + };
> > +
> > + pins-ds {
> > + pinmux = <PINMUX_GPIO167__FUNC_MSDC0_DSL>;
> > + drive-strength = <8>;
> > + bias-pull-down = <MTK_PUPD_SET_R1R0_10>;
> > + };
> > +
> > + pins-rst {
> > + pinmux =
> > <PINMUX_GPIO160__FUNC_MSDC0_RSTB>;
> > + bias-pull-up = <MTK_PUPD_SET_R1R0_00>;
> > + };
> > + };
> > +
> > + mmc1_default_pins: mmc1-default-pins {
> > + pins-clk {
> > + pinmux = <PINMUX_GPIO169__FUNC_MSDC1_CLK>;
> > + drive-strength = <6>;
> > + bias-pull-down = <MTK_PUPD_SET_R1R0_10>;
> > + };
> > +
> > + pins-cmd-dat {
> > + pinmux =
> > <PINMUX_GPIO170__FUNC_MSDC1_DAT0>,
> > +
> > <PINMUX_GPIO171__FUNC_MSDC1_DAT1>,
> > +
> > <PINMUX_GPIO172__FUNC_MSDC1_DAT2>,
> > +
> > <PINMUX_GPIO173__FUNC_MSDC1_DAT3>,
> > + <PINMUX_GPIO168__FUNC_MSDC1_CMD>;
> > + input-enable;
> > + drive-strength = <6>;
> > + bias-pull-up = <MTK_PUPD_SET_R1R0_01>;
> > + };
> > +
> > + pins-insert {
> > + pinmux = <PINMUX_GPIO2__FUNC_GPIO2>;
> > + bias-pull-up;
> > + };
> > + };
> > +
> > + mmc1_uhs_pins: mmc1-uhs-pins {
> > + pins-clk {
> > + pinmux = <PINMUX_GPIO169__FUNC_MSDC1_CLK>;
> > + drive-strength = <8>;
> > + bias-pull-down = <MTK_PUPD_SET_R1R0_10>;
> > + };
> > +
> > + pins-cmd-dat {
> > + pinmux =
> > <PINMUX_GPIO170__FUNC_MSDC1_DAT0>,
> > +
> > <PINMUX_GPIO171__FUNC_MSDC1_DAT1>,
> > +
> > <PINMUX_GPIO172__FUNC_MSDC1_DAT2>,
> > +
> > <PINMUX_GPIO173__FUNC_MSDC1_DAT3>,
> > + <PINMUX_GPIO168__FUNC_MSDC1_CMD>;
> > + input-enable;
> > + drive-strength = <8>;
> > + bias-pull-up = <MTK_PUPD_SET_R1R0_01>;
> > + };
>
> Don't we also need pins-insert here? (to match mmc1-default-pins)
>
From what I've found, it was done this way for other board devicetrees
to avoid possible reconfiguration happen for the card detection pin
while switching to UHS and causing a switch failure.
Also, what you declare in pinmux nodes is how the pin configuration
should change in a specific mode and you declare only what changes, and
not what stay the same.
> I was having trouble with the CD input pin not working in U-Boot
> until I added it.
I checked and debugged this on my board and did not get that kind of
issue, whether this pin config is not present for uhs state or if I add
it.
When inserting my sd card or when I boot with it already inserted, the
mtk-sd driver first sets the pinctrl state to default before switching
to ufs. The GPIO02 pin config is also OK in both states.
The mt8189 pinctrl driver seems to apply a default config for this pin
that is the same as the one that is set here.
There might be u-boot particularities that could explain it fixes your
issue.
Regards,
Louis-Alexis
>
> > + };
> > +
next prev parent reply other threads:[~2026-03-20 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 13:59 [PATCH 0/4] Add support for the Mediatek Genio 520-EVK and 720-EVK boards Louis-Alexis Eyraud
2025-12-03 13:59 ` [PATCH 1/4] dt-bindings: serial: mediatek,uart: Add compatible for MT8189 SoC Louis-Alexis Eyraud
2025-12-03 20:21 ` Krzysztof Kozlowski
2025-12-10 16:19 ` Macpaul Lin (林智斌)
2025-12-03 13:59 ` [PATCH 2/4] dt-bindings: arm: mediatek: add compatibles for Mediatek Genio 520/720-EVK boards Louis-Alexis Eyraud
2025-12-03 20:23 ` Krzysztof Kozlowski
2025-12-03 13:59 ` [PATCH 3/4] arm64: dts: mediatek: add device-tree for Genio 720-EVK board Louis-Alexis Eyraud
2025-12-03 20:25 ` Krzysztof Kozlowski
2026-02-20 0:09 ` David Lechner
2026-03-20 14:06 ` Louis-Alexis Eyraud
2026-03-13 0:26 ` David Lechner
2026-03-20 12:37 ` Louis-Alexis Eyraud [this message]
2026-03-20 13:35 ` David Lechner
2025-12-03 13:59 ` [PATCH 4/4] arm64: dts: mediatek: add device-tree for Genio 520-EVK board Louis-Alexis Eyraud
2025-12-05 22:36 ` [PATCH 0/4] Add support for the Mediatek Genio 520-EVK and 720-EVK boards Rob Herring
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=7d1e52c0b9c3a6d30e9db617b9bcfa23ed9046b5.camel@collabora.com \
--to=louisalexis.eyraud@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.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®