From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v4 0/4] UHS-I SDR-104 support for sh_mobile_sdhi
Date: Thu, 11 Aug 2016 10:43:02 +0200 [thread overview]
Message-ID: <20160811084301.GF30475@verge.net.au> (raw)
In-Reply-To: <20160810131224.GB1741@katana>
On Wed, Aug 10, 2016 at 03:12:24PM +0200, Wolfram Sang wrote:
> Hi Simon,
>
> > In this patchset I have attempted to address all review received
> > for the v3 patch-set. I also believe that I have resolved a problem
> > where tuning would timeout under some circumstances: this seems to
> > have been due to several bugs introduced between v1 and v3.
>
> So, you didn't see timeouts anymore?
Yes, that is correct.
I have not seen them at all with this patchset.
I will extend my testing as I integrate these changes on other SoCs and boards.
> > * Currently I am seeing speeds of up to 48MB/s with these patches and
> > 30MB/s without using a SanDisk Extreme Pro 8Gb microSDHC UHS-1 card.
> >
> > * I am also seeing 45MB/s with these patches and 34MB/s without using
> > a SanDisk Ultra 64Gb microSDXC UHS-1 card.
>
> I got similar numbers for my SanDisk and Samsung cards. While the SDR104
> speed is not that what I hoped for, it is still an improvement over
> SDR50. We are currently investigating if DMA causes a bottleneck
> somewhere perhaps. Except for a minor comment, I'd think these patches
> are good to go in and we could improve incrementally from here:
>
> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> Maybe Ulf can have another high-level view on those. I guess he is more
> experienced with the tuning stuff?
Yes, of course such input would be welcome.
I'd like to work towards getting these changes merged.
prev parent reply other threads:[~2016-08-11 8:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 4:13 [PATCH v4 0/4] UHS-I SDR-104 support for sh_mobile_sdhi Simon Horman
2016-07-27 4:13 ` [PATCH v4 1/4] mmc: tmio: enhance illegal sequence handling Simon Horman
2016-07-27 4:13 ` [PATCH v4 2/4] mmc: tmio: Add tuning support Simon Horman
2016-08-10 13:10 ` Wolfram Sang
2016-08-22 13:39 ` Ulf Hansson
2016-08-23 13:52 ` Simon Horman
2016-08-23 15:02 ` Ulf Hansson
2016-08-25 12:04 ` Simon Horman
2016-08-26 8:01 ` Ulf Hansson
2016-08-29 12:05 ` Simon Horman
2016-08-29 14:05 ` Ulf Hansson
2016-08-30 20:51 ` Simon Horman
2016-08-31 7:38 ` Ulf Hansson
2016-09-01 6:46 ` Simon Horman
2016-09-01 8:37 ` Simon Horman
2016-09-01 9:55 ` Ulf Hansson
2016-09-01 14:19 ` Simon Horman
2016-07-27 4:13 ` [PATCH v4 3/4] mmc: sh_mobile_sdhi: " Simon Horman
2016-07-28 0:12 ` Simon Horman
2016-07-27 4:13 ` [PATCH v4 4/4] ARM: dts: r8a7790: lager: Enable UHS-I SDR-104 Simon Horman
2016-08-10 13:12 ` [PATCH v4 0/4] UHS-I SDR-104 support for sh_mobile_sdhi Wolfram Sang
2016-08-11 8:43 ` 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=20160811084301.GF30475@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.de \
/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.