From: Marek Vasut <marek.vasut@gmail.com>
To: Simon Horman <horms@verge.net.au>, Wolfram Sang <wsa@the-dreams.de>
Cc: 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 14:03:30 +0100 [thread overview]
Message-ID: <b43d1c03-05c1-d7db-0f4d-712e2d3e608c@gmail.com> (raw)
In-Reply-To: <20181031124628.buaiuof5ssllalwo@verge.net.au>
On 10/31/2018 01:46 PM, Simon Horman wrote:
> 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?
I'm not sure I understand this remark. Anyway, I'll be spinning a V2 of
the patchset, which will be a single patch.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-10-31 22:01 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 [this message]
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=b43d1c03-05c1-d7db-0f4d-712e2d3e608c@gmail.com \
--to=marek.vasut@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox