All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa@the-dreams.de>
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:46:33 +0100	[thread overview]
Message-ID: <20181031124628.buaiuof5ssllalwo@verge.net.au> (raw)
In-Reply-To: <20181029085721.GC4101@kunai>

On Mon, Oct 29, 2018 at 08:57:21AM +0000, Wolfram Sang wrote:
> 
> > > <&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.

I agree we can add stuff later if we need it.
But can we discuss this in the context of describing the hardware?

  reply	other threads:[~2018-10-31 21:44 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 [this message]
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=20181031124628.buaiuof5ssllalwo@verge.net.au \
    --to=horms@verge.net.au \
    --cc=geert+renesas@glider.be \
    --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=wsa@the-dreams.de \
    --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.