From: Simon Horman <horms@verge.net.au>
To: linux-renesas-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Magnus Damm <magnus.damm@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH/RFT 0/2] ARM: dts: gose: Enable UHS-I SDR-50 and SDR-104
Date: Thu, 11 May 2017 17:48:31 +0200 [thread overview]
Message-ID: <20170511154831.GI21895@verge.net.au> (raw)
In-Reply-To: <1492494939-24568-1-git-send-email-horms+renesas@verge.net.au>
On Tue, Apr 18, 2017 at 02:55:37PM +0900, Simon Horman wrote:
> Enable
> - SDR-50 and SDR-104 for SDHI0 and;
> - SDR-50 for SDHI1
>
> Verified:
> - SDR104 for SDHI0
> - SDR50 for SDHI1
> - Results comprable to those listed for other Renesas R-Car Gen2 boards on
> http://elinux.org/Tests:SD-SDHI-SDR104
> Untested:
> SDR50 for SDHI3
> - HS C4 card present in slot on board which I access remotely
The above should read SDHI2 rather than SDHI3.
I have now been able to test SDHI2 and have queued up this series
with Wolfram's Acks.
> Simon Horman (2):
> ARM: dts: r8a7793: set maximum frequency for SDHI clocks
> ARM: dts: gose: Enable UHS-I SDR-50 and SDR-104
>
> arch/arm/boot/dts/r8a7793-gose.dts | 34 +++++++++++++++++++++++++++++++---
> arch/arm/boot/dts/r8a7793.dtsi | 3 +++
> 2 files changed, 34 insertions(+), 3 deletions(-)
>
> --
> 2.7.0.rc3.207.g0ac5344
>
prev parent reply other threads:[~2017-05-11 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 5:55 [PATCH/RFT 0/2] ARM: dts: gose: Enable UHS-I SDR-50 and SDR-104 Simon Horman
2017-04-18 5:55 ` [PATCH/RFT 1/2] ARM: dts: r8a7793: set maximum frequency for SDHI clocks Simon Horman
2017-04-19 7:36 ` Wolfram Sang
2017-04-18 5:55 ` [PATCH/RFT 2/2] ARM: dts: gose: Enable UHS-I SDR-50 and SDR-104 Simon Horman
2017-04-19 7:30 ` Wolfram Sang
2017-05-11 15:48 ` Simon Horman [this message]
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=20170511154831.GI21895@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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).