From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [RFT] arm64: dts: renesas: salvator-common: enable SDR104 for SD cards
Date: Thu, 3 Aug 2017 17:54:00 +0200 [thread overview]
Message-ID: <20170803155357.GA3826@verge.net.au> (raw)
In-Reply-To: <20170803074351.GC19671@verge.net.au>
On Thu, Aug 03, 2017 at 09:43:51AM +0200, Simon Horman wrote:
> On Wed, Aug 02, 2017 at 10:13:11PM +0200, Wolfram Sang wrote:
> > Tests showed that SDHI driver problems have been solved and SDR104 works
> > now reliably on both Salvator-X SD card slots, both with an R-Car H3
> > (r8a7795 ES1.0) and R-Car M3 (r8a7796 ES 1.0). So, finally, enable it.
> >
> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > ---
> >
> > Awesome, awesome! For the last two days, I did various tests with my boards and
> > SD cards and SDR104 worked absolutely reliably :D Even the problematic card I
> > had works flawlessly. I couldn't trigger the known failures anymore. Although I
> > tried, I can't point to a single patch which "fixed" the issue. It is the
> > constant work on dealing with smaller issues which makes SDR104 work at the end
> > of the day. However, two patches are likely a bigger part of the cake:
> >
> > 43b0b361b01700 ("mmc: tmio: always get number of taps")
> > -> Already upstream. This fixed retuning on card changes.
> >
> > 85b81aa16ec4ed ("mmc: tmio: fix CMD12 (STOP) handling")
> > -> In mmc/next. This allows to handle tuning errors gracefully and to retune.
> >
> > With the freshly submitted Gen3 DMA patches, we also get nice transfer speeds :)
> >
> > This patch is based on renesas-drivers/master as of today. A branch for testing
> > can be found here:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/v8-sdr104
> >
> > All patches needed for reliable SDR104 are already upstream or in mmc/next. The
> > above branch only adds another patch to enable DMA on Gen3. It is not strictly
> > needed, but very nice to have. I think it would be cool to get both patches
> > into v4.14.
> >
> > Looking forward to other testers. Simon, do you have some time for this?
>
> Yes, I should be able to run this through my - until now thought to be
> broken - test case this week.
>
> It would be very nice to be able to get closure on this :)
Awesome indeed!
I have tested this using my test-case which is to remove and then
re-insert a Samsung MB-SD32D/EU card. Slot SDHI3 was used although I expect
that is not an important parameter.
A bisection indicates the above test works since
85b81aa16ec4ed ("mmc: tmio: fix CMD12 (STOP) handling")
which was included in v4.12 and highlighted by you above.
Tested-by: Simon Horman <horms@verge.net.au>
I will apply this for v4.14 in the near future.
next prev parent reply other threads:[~2017-08-03 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 20:13 [RFT] arm64: dts: renesas: salvator-common: enable SDR104 for SD cards Wolfram Sang
2017-08-03 7:43 ` Simon Horman
2017-08-03 15:54 ` Simon Horman [this message]
2017-08-03 15:55 ` Simon Horman
2017-08-08 18:54 ` Wolfram Sang
2017-08-14 5:10 ` Simon Horman
2017-08-14 15:46 ` Wolfram Sang
2017-08-17 8:44 ` Simon Horman
2017-08-29 15:42 ` Wolfram Sang
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=20170803155357.GA3826@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.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