From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: eagle-function-expansion: add eMMC support
Date: Fri, 10 Oct 2025 09:35:39 +0200 [thread overview]
Message-ID: <CAMuHMdXrjkbyXjTekjifbODcPPP09mVxVH+EDpMM9F0A8hXS1A@mail.gmail.com> (raw)
In-Reply-To: <aOf0wSc5rgve30af@shikoro>
Hi Wolfram,
On Thu, 9 Oct 2025 at 19:45, Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> On Thu, Oct 09, 2025 at 05:18:23PM +0200, Geert Uytterhoeven wrote:
> > On Tue, 23 Sept 2025 at 18:17, Wolfram Sang
> > <wsa+renesas@sang-engineering.com> wrote:
> > > Add pinmuxing and configuration of the MMC-capable SDHI instance to make
> > > use of the eMMC.
> > >
> > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> >
> > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > i.e. will queue in renesas-devel for v6.19.
>
> Thanks. However, I just saw that the node name in pinctrl is bogus,
> sorry :( mmc_3_3v is plain wrong, mmc_1_8v would be better, but
> actually, I think it should be just mmc0. Voltage switch is not
> supported on that board.
Thanks, will fix that up to "mmc" (which is what the others are using).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2025-10-10 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 16:15 [PATCH] arm64: dts: renesas: eagle-function-expansion: add eMMC support Wolfram Sang
2025-10-09 15:18 ` Geert Uytterhoeven
2025-10-09 17:45 ` Wolfram Sang
2025-10-10 7:35 ` Geert Uytterhoeven [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=CAMuHMdXrjkbyXjTekjifbODcPPP09mVxVH+EDpMM9F0A8hXS1A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).