From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [PATCH] arm64: dts: renesas: condor: switch eMMC bus to 1V8
Date: Tue, 20 Apr 2021 09:04:30 +0200 [thread overview]
Message-ID: <CAMuHMdXd25JBitCXQaxXvtpT2GUm02BNk2y4s+wOOfNew2FEUA@mail.gmail.com> (raw)
In-Reply-To: <20210419143858.39401-1-wsa+renesas@sang-engineering.com>
On Mon, Apr 19, 2021 at 6:07 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> The eMMC card has two supplies, VCC and VCCQ. The VCC supplies the NAND
> array and the VCCQ supplies the bus. On Condor, the VCC is connected to
> 3.3V rail, while the VCCQ is connected to 1.8V rail. Adjust the pinmux
> to match the bus, which is always operating in 1.8V mode.
>
> While at it, deduplicate the pinmux entries, which are now the same for
> both default and UHS modes. We still need the two pinctrl entries to
> match the bindings though.
>
> Thanks to Marek Vasut for this commit description from 5f65328df3f5.
... from commit 5f65328df3f5cd25 ("arm64: dts: renesas: Switch eMMC
bus to 1V8 on Salvator-X and ULCB")
> 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 v5.14, with the above augmented.
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:[~2021-04-20 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 14:38 [PATCH] arm64: dts: renesas: condor: switch eMMC bus to 1V8 Wolfram Sang
2021-04-20 7:04 ` 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=CAMuHMdXd25JBitCXQaxXvtpT2GUm02BNk2y4s+wOOfNew2FEUA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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 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.