From: Wolfram Sang <wsa@the-dreams.de>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/3] ARM: dts: iwg20m: Enable SDHI0 controller
Date: Mon, 21 Aug 2017 10:33:57 +0200 [thread overview]
Message-ID: <20170821083357.GC2418@katana> (raw)
In-Reply-To: <KL1PR06MB1702AC0B4C40F48A80505B74B8870@KL1PR06MB1702.apcprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
> > > +vmmc-supply = <®_3p3v>;
> > > +vqmmc-supply = <®_3p3v>;
> >
> > Just to make sure: No 1.8V and UHS support (SDR50/104)? Or is this to be
> > tested and added later?
>
> Thanks. The current hardware doesn't support 1.8V switching for SDHI0. There is a plan to
> add this in future board varient, at that time we will add UHS support.
I see. Thanks for the info, patch looks good to me then:
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-21 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 11:49 [PATCH 0/3] Add SDHI Support Biju Das
2017-08-14 11:49 ` [PATCH 1/3] ARM: dts: r8a7743: Add SDHI controllers Biju Das
2017-08-14 11:49 ` [PATCH 2/3] ARM: dts: iwg20m: Enable SDHI0 controller Biju Das
2017-08-21 8:28 ` Wolfram Sang
2017-08-21 8:31 ` Biju Das
2017-08-21 8:33 ` Wolfram Sang [this message]
[not found] ` <1502711389-16040-1-git-send-email-biju.das-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-08-14 11:49 ` [PATCH 3/3] ARM: dts: iwg20d-q7: Add SDHI1 support Biju Das
[not found] ` <1502711389-16040-4-git-send-email-biju.das-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-08-21 8:34 ` Wolfram Sang
2017-08-22 8:02 ` [PATCH 0/3] Add SDHI Support Simon Horman
[not found] ` <20170822080258.GF30838-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-08-22 8:13 ` Biju Das
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=20170821083357.GC2418@katana \
--to=wsa@the-dreams.de \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).