From: Ulf Hansson <ulf.hansson@linaro.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [PATCH 0/5] mmc: renesas_sdhi: prepare for recent HS400 updates
Date: Tue, 10 Dec 2019 14:09:51 +0100 [thread overview]
Message-ID: <CAPDyKFpXanmDQq-minnX4KNLVSMatOQRnuT59sDdAZC_MDkp8A@mail.gmail.com> (raw)
In-Reply-To: <20191203200513.1758-1-wsa+renesas@sang-engineering.com>
On Tue, 3 Dec 2019 at 21:05, Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
>
> Due to recent datasheet updates and other internal documents, HS400
> support for SDHI needs some refactoring. These patches are the
> prerequisites for that. The first four patches only refactor code, the
> last one does a minor update already.
>
> This series has been tested on Renesas Salvator-XS with R-Car M3-N and
> H3 ES2.0 with tests I was able to carry out locally here.
>
> I will send more advanced patches on top of this series as RFC later.
>
> A branch with all the patches applied can be found here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/sdhi/new_manual_calib
>
> Wolfram Sang (5):
> mmc: renesas_sdhi: keep sorting for quirk entries
> mmc: renesas_sdhi: make warning more precise
> mmc: renesas_sdhi: make quirks info accessible outside probe()
> mmc: renesas_sdhi: remove 4taps as a TMIO flag
> mmc: renesas_sdhi: use recent tap values for HS400
>
> drivers/mmc/host/renesas_sdhi.h | 10 ++++++--
> drivers/mmc/host/renesas_sdhi_core.c | 23 ++++++++-----------
> drivers/mmc/host/renesas_sdhi_internal_dmac.c | 2 +-
> include/linux/mfd/tmio.h | 3 ---
> 4 files changed, 19 insertions(+), 19 deletions(-)
>
> --
> 2.20.1
>
Applied for next and by fixing up the comments for patch 4, thanks!
Kind regards
Uffe
next prev parent reply other threads:[~2019-12-10 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 20:05 [PATCH 0/5] mmc: renesas_sdhi: prepare for recent HS400 updates Wolfram Sang
2019-12-03 20:05 ` [PATCH 1/5] mmc: renesas_sdhi: keep sorting for quirk entries Wolfram Sang
2019-12-04 9:26 ` Geert Uytterhoeven
2019-12-05 12:13 ` Yoshihiro Shimoda
2019-12-03 20:05 ` [PATCH 2/5] mmc: renesas_sdhi: make warning more precise Wolfram Sang
2019-12-04 9:27 ` Geert Uytterhoeven
2019-12-05 12:13 ` Yoshihiro Shimoda
2019-12-03 20:05 ` [PATCH 3/5] mmc: renesas_sdhi: make quirks info accessible outside probe() Wolfram Sang
2019-12-04 9:28 ` Geert Uytterhoeven
2019-12-05 12:14 ` Yoshihiro Shimoda
2019-12-03 20:05 ` [PATCH 4/5] mmc: renesas_sdhi: remove 4taps as a TMIO flag Wolfram Sang
2019-12-04 9:29 ` Geert Uytterhoeven
2019-12-04 9:47 ` Sergei Shtylyov
2019-12-05 12:16 ` Yoshihiro Shimoda
2019-12-03 20:05 ` [PATCH/RFT 5/5] mmc: renesas_sdhi: use recent tap values for HS400 Wolfram Sang
2019-12-05 12:45 ` Yoshihiro Shimoda
2019-12-10 13:09 ` Ulf Hansson [this message]
2019-12-10 22:21 ` [PATCH 0/5] mmc: renesas_sdhi: prepare for recent HS400 updates 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=CAPDyKFpXanmDQq-minnX4KNLVSMatOQRnuT59sDdAZC_MDkp8A@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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).