From: Ulf Hansson <ulf.hansson@linaro.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Simon Horman <horms+renesas@verge.net.au>
Cc: Magnus Damm <magnus.damm@gmail.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] mmc: renesas_sdhi: add eMMC HS400 mode support
Date: Tue, 27 Feb 2018 08:53:17 +0100 [thread overview]
Message-ID: <CAPDyKFryhg=5G9G3ss3hFSAuri1-_y0uu7ZK=PNGJ0TF=-__DA@mail.gmail.com> (raw)
In-Reply-To: <20180213123358.13212-1-horms+renesas@verge.net.au>
On 13 February 2018 at 13:33, Simon Horman <horms+renesas@verge.net.au> wrote:
> Hi,
>
> this patch-set provides SDHI driver support for eMMC HS400.
>
> Based on mmc/next
>
> Dependencies for applying these patches: none
>
> Dependencies to test eMMC HS400:
> * [PATCH] clk: renesas: rcar-gen3: Fix SD divider setting
> * [PATCH v2] arm64: dts: salvator-common: Enable HS400 of SDHI2
>
> To assist testing and review this patch and the above mentioned
> dependencies, which are necessary and sufficient to enable HS400 on H3 /
> Salvator-X, M3-W 1.0 / Salvator-X and H3 ES2.0 Salvator-XS are available
> at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git topic/hs400-v3
>
> Changes since v2:
> * Consolidate disable_scc and reset_hs400_mode into reset_hs400_tuning
> callback
> * Reuse renesas_sdhi_reset_hs400_mode() in renesas_sdhi_hw_reset()
> * Factor out renesas_sdhi_reset_scc()
>
> Changes since v1:
> * Use updated code from BSP v3.6.0
> * Ironed out dependencies, eMMC HS400 is now working on
> H3 / Salvator-X, M3-W 1.0 / Salvator-X and H3 ES2.0 Salvator-XS.
>
> Masaharu Hayakawa (2):
> mmc: tmio: add eMMC HS400 mode support
> mmc: renesas_sdhi: add eMMC HS400 mode support
>
> drivers/mmc/host/renesas_sdhi_core.c | 133 +++++++++++++++++++++++++++++------
> drivers/mmc/host/tmio_mmc.h | 5 ++
> drivers/mmc/host/tmio_mmc_core.c | 24 ++++++-
> 3 files changed, 138 insertions(+), 24 deletions(-)
>
> --
> 2.11.0
>
Simon, Wolfram,
Is this ready to be queued up for next? It looks good to me.
Kind regards
Uffe
next prev parent reply other threads:[~2018-02-27 7:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:33 [PATCH v3 0/2] mmc: renesas_sdhi: add eMMC HS400 mode support Simon Horman
2018-02-13 12:33 ` [PATCH v3 1/2] mmc: tmio: " Simon Horman
2018-02-13 12:33 ` [PATCH v3 2/2] mmc: renesas_sdhi: " Simon Horman
2018-02-27 7:53 ` Ulf Hansson [this message]
2018-02-27 8:26 ` [PATCH v3 0/2] " Simon Horman
2018-02-27 9:07 ` Wolfram Sang
2018-02-27 10:13 ` Ulf Hansson
2018-02-27 13:02 ` Wolfram Sang
2018-03-27 11:12 ` Simon Horman
2018-04-05 7:30 ` Ulf Hansson
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='CAPDyKFryhg=5G9G3ss3hFSAuri1-_y0uu7ZK=PNGJ0TF=-__DA@mail.gmail.com' \
--to=ulf.hansson@linaro.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=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 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.