All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-mmc@vger.kernel.org,
	Marek Vasut <marek.vasut+renesas@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Simon Horman <horms+renesas@verge.net.au>,
	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: Mon, 29 Oct 2018 08:57:21 +0000	[thread overview]
Message-ID: <20181029085721.GC4101@kunai> (raw)
In-Reply-To: <f63a5c27-ea7d-e1f0-9bbb-211f56be8ad9@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 493 bytes --]


> > <&sdhi2_pins>;". So, basically the same phandles for both pinctrls. We
> > can re-add the second one when we need it.
> 
> I wonder if removing the sdhi2_pins_uhs is what we want to do, given
> that we might need to adjust TDSEL or pull resistor configurations for
> the HS200/HS400 modes in the future.

Well, quoting myself "We can re-add the second one when we need it". It
is possible but a tad unlikely. That's my take on it but it is
ultimately up to Simon, of course.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-10-29 17:45 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 [this message]
2018-10-31 12:46         ` Simon Horman
2018-10-31 13:03           ` Marek Vasut
2018-10-31 13:14           ` Wolfram Sang
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=20181029085721.GC4101@kunai \
    --to=wsa@the-dreams.de \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@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.