From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Simon Horman" <horms+renesas@verge.net.au>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Linux MMC List" <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Ai Kyuse" <ai.kyuse.uw@renesas.com>
Subject: Re: [PATCH v8 6/6] mmc: sh_mobile_sdhi: Add tuning support
Date: Thu, 12 Jan 2017 14:03:24 +0100 [thread overview]
Message-ID: <20170112130324.GA3328@katana> (raw)
In-Reply-To: <CAMuHMdW4r1gmJDgFxcHNNys70xipMb7BKsv_7ZZNPQAX+SV6pQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
> I'll bring my Koelsch.
Great. I *think* one Koelsch will do, but if it is not too much of a
problem, double-checking with a second board won't hurt. So, since Geert
will probably bring all necessary cables and supplies, maybe you can
pack the board nonetheless? But having one Koelsch already is really
good!
> AFAIK, Wolfram is interested in "as many SD cards", not "as many Koelsch
> boards".
1st: as many Gen2 boards as possible (one per Gen2 SoC version would be
awesome!) Gose, Alt anyone?
For those, I'll bring my SanDisk card which causes issues when ejecting
on all my boards. This is my main target.
2nd: as many SD cards as possible
This is a secondary target, but trying to find other issues/other type
of cards with same issues will be helpful, too.
Thanks,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-12 13:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 14:15 [PATCH v8 0/6] UHS-I SDR-104 support for sh_mobile_sdhi Simon Horman
2016-11-03 14:15 ` [PATCH v8 1/6] mmc: core: Add helper to see if a host can be retuned Simon Horman
2016-11-03 14:16 ` [PATCH v8 2/6] mmc: tmio: enhance illegal sequence handling Simon Horman
2016-11-03 14:16 ` [PATCH v8 3/6] mmc: tmio: document mandatory and optional callbacks Simon Horman
2016-11-03 14:16 ` [PATCH v8 4/6] mmc: tmio: Add hw reset support Simon Horman
2016-11-03 14:16 ` [PATCH v8 5/6] mmc: tmio: Add tuning support Simon Horman
2016-11-03 14:16 ` [PATCH v8 6/6] mmc: sh_mobile_sdhi: " Simon Horman
2017-01-10 21:08 ` Niklas Söderlund
2017-01-10 22:30 ` Wolfram Sang
2017-01-11 8:35 ` Niklas Söderlund
2017-01-11 8:42 ` Geert Uytterhoeven
2017-01-11 9:17 ` Niklas Söderlund
2017-01-11 15:05 ` Wolfram Sang
2017-01-11 15:57 ` Niklas Söderlund
2017-01-11 15:59 ` Geert Uytterhoeven
2017-01-11 17:34 ` Wolfram Sang
2017-01-12 11:17 ` Niklas Söderlund
2017-01-12 11:23 ` Geert Uytterhoeven
2017-01-12 13:03 ` Wolfram Sang [this message]
2017-01-17 11:29 ` Niklas Söderlund
2017-01-23 11:16 ` Wolfram Sang
2017-01-31 20:56 ` Niklas Söderlund
2017-01-26 9:58 ` Simon Horman
2016-11-10 11:45 ` [PATCH v8 0/6] UHS-I SDR-104 support for sh_mobile_sdhi Wolfram Sang
2016-11-10 22:21 ` Ulf Hansson
2016-11-11 7:20 ` Simon Horman
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=20170112130324.GA3328@katana \
--to=wsa@the-dreams.de \
--cc=ai.kyuse.uw@renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=ulf.hansson@linaro.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).