From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms@verge.net.au>
Cc: Marek Vasut <marek.vasut@gmail.com>,
linux-mmc@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: renesas: salvator: Switch eMMC bus to 1V8
Date: Wed, 31 Oct 2018 13:14:09 +0000 [thread overview]
Message-ID: <20181031131409.GB1487@kunai> (raw)
In-Reply-To: <20181031124628.buaiuof5ssllalwo@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
> But can we discuss this in the context of describing the hardware?
The SDHI node needs two kinds of pinmux settings, one for normal speeds
and one for highspeeds. They might differ in supplied voltage, i.e. 3v3
and 1v8. This eMMC always works with 1v8, so both settings needed by the
SDHI node are the same currently. That might change if we add new
features to pinmux nodes like TDSEL/capacity support. My guess is that
this is not so likely to happen so I suggested using just one node.
But it has a taste of bike-shedding to it :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-31 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 16:34 [PATCH 1/2] arm64: dts: renesas: ulcb: Switch eMMC bus to 1V8 Marek Vasut
2018-10-27 16:34 ` [PATCH 2/2] arm64: dts: renesas: salvator: " Marek Vasut
2018-10-28 21:34 ` Wolfram Sang
2018-10-29 8:01 ` Marek Vasut
2018-10-29 8:57 ` Wolfram Sang
2018-10-31 12:46 ` Simon Horman
2018-10-31 13:03 ` Marek Vasut
2018-10-31 13:14 ` Wolfram Sang [this message]
2018-11-04 20:38 ` Marek Vasut
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=20181031131409.GB1487@kunai \
--to=wsa@the-dreams.de \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.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.