From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Dirk Behme <dirk.behme@de.bosch.com>,
Chris Brandt <chris.brandt@renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH] mmc: renesas_sdhi: use extra flag for CBSY usage
Date: Thu, 10 Aug 2017 09:58:50 +0200 [thread overview]
Message-ID: <20170810075850.GD16647@verge.net.au> (raw)
In-Reply-To: <20170809190041.1052-1-wsa+renesas@sang-engineering.com>
On Wed, Aug 09, 2017 at 09:00:41PM +0200, Wolfram Sang wrote:
> There is one SDHI instance on Gen2 which does not have the CBSY bit.
> So, turn CBSY usage into an extra flag and set it accordingly. This has
> the additional advantage that we can also set it for other incarnations
> later.
What is the run-time effect, if any, of this change?
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Code looks good:
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> ---
>
> Tested on a M3-W Salvator-X and H2 Lager (with both SDHI instances). I could
> move large files around without problems. Note that on the special incarnation
> without the CBSY bit, the old code still worked, so there might be a CBSY bit.
> But it is not documented, so we better play safe.
>
> Chris: according to the specs I have, we can enable it for RZ as well. I'll
> send a patch for that in a minute. If you could test this on top of this one,
> that would be much appreciated! Thanks.
I take it from the above you did a pass of the available documentation to
see which SoCs support this feature. If so, thanks!
> drivers/mmc/host/renesas_sdhi_core.c | 6 +++++-
> drivers/mmc/host/renesas_sdhi_internal_dmac.c | 3 ++-
> drivers/mmc/host/renesas_sdhi_sys_dmac.c | 6 ++++--
> include/linux/mfd/tmio.h | 3 +++
> 4 files changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mmc/host/renesas_sdhi_core.c b/drivers/mmc/host/renesas_sdhi_core.c
> index a252145097d6a5..e46504edc9fcb4 100644
> --- a/drivers/mmc/host/renesas_sdhi_core.c
> +++ b/drivers/mmc/host/renesas_sdhi_core.c
> @@ -429,7 +429,7 @@ static int renesas_sdhi_write16_hook(struct tmio_mmc_host *host, int addr)
> case CTL_TRANSACTION_CTL:
> case CTL_DMA_ENABLE:
> case EXT_ACC:
> - if (host->pdata->flags & TMIO_MMC_MIN_RCAR2)
> + if (host->pdata->flags & TMIO_MMC_HAVE_CBSY)
> bit = TMIO_STAT_CMD_BUSY;
> /* fallthrough */
> case CTL_SD_CARD_CLK_CTL:
> @@ -589,6 +589,10 @@ int renesas_sdhi_probe(struct platform_device *pdev,
> if (ret < 0)
> goto efree;
>
> + /* One Gen2 SDHI incarnation does NOT have a CBSY bit */
> + if (sd_ctrl_read16(host, CTL_VERSION) == SDHI_VER_GEN2_SDR50)
> + mmc_data->flags &= ~TMIO_MMC_HAVE_CBSY;
> +
> /* Enable tuning iff we have an SCC and a supported mode */
> if (of_data && of_data->scc_offset &&
> (host->mmc->caps & MMC_CAP_UHS_SDR104 ||
> diff --git a/drivers/mmc/host/renesas_sdhi_internal_dmac.c b/drivers/mmc/host/renesas_sdhi_internal_dmac.c
> index 6717003888e292..fa4e71d3b47d47 100644
> --- a/drivers/mmc/host/renesas_sdhi_internal_dmac.c
> +++ b/drivers/mmc/host/renesas_sdhi_internal_dmac.c
> @@ -72,7 +72,8 @@ static struct renesas_sdhi_scc rcar_gen3_scc_taps[] = {
>
> static const struct renesas_sdhi_of_data of_rcar_gen3_compatible = {
> .tmio_flags = TMIO_MMC_HAS_IDLE_WAIT | TMIO_MMC_WRPROTECT_DISABLE |
> - TMIO_MMC_CLK_ACTUAL | TMIO_MMC_MIN_RCAR2,
> + TMIO_MMC_CLK_ACTUAL | TMIO_MMC_HAVE_CBSY |
> + TMIO_MMC_MIN_RCAR2,
> .capabilities = MMC_CAP_SD_HIGHSPEED | MMC_CAP_SDIO_IRQ |
> MMC_CAP_CMD23,
> .bus_shift = 2,
Keeping the above of_rcar_gen3_compatible structure in sync with the one
below may get painful at some point. Perhaps we should consider a common
location for it? (Yes, I know this is my handiwork)
> diff --git a/drivers/mmc/host/renesas_sdhi_sys_dmac.c b/drivers/mmc/host/renesas_sdhi_sys_dmac.c
> index 718cb8a9d2ce8d..9b77f521cd2c2f 100644
> --- a/drivers/mmc/host/renesas_sdhi_sys_dmac.c
> +++ b/drivers/mmc/host/renesas_sdhi_sys_dmac.c
> @@ -58,7 +58,8 @@ static struct renesas_sdhi_scc rcar_gen2_scc_taps[] = {
>
> static const struct renesas_sdhi_of_data of_rcar_gen2_compatible = {
> .tmio_flags = TMIO_MMC_HAS_IDLE_WAIT | TMIO_MMC_WRPROTECT_DISABLE |
> - TMIO_MMC_CLK_ACTUAL | TMIO_MMC_MIN_RCAR2,
> + TMIO_MMC_CLK_ACTUAL | TMIO_MMC_HAVE_CBSY |
> + TMIO_MMC_MIN_RCAR2,
> .capabilities = MMC_CAP_SD_HIGHSPEED | MMC_CAP_SDIO_IRQ |
> MMC_CAP_CMD23,
> .dma_buswidth = DMA_SLAVE_BUSWIDTH_4_BYTES,
> @@ -78,7 +79,8 @@ static struct renesas_sdhi_scc rcar_gen3_scc_taps[] = {
>
> static const struct renesas_sdhi_of_data of_rcar_gen3_compatible = {
> .tmio_flags = TMIO_MMC_HAS_IDLE_WAIT | TMIO_MMC_WRPROTECT_DISABLE |
> - TMIO_MMC_CLK_ACTUAL | TMIO_MMC_MIN_RCAR2,
> + TMIO_MMC_CLK_ACTUAL | TMIO_MMC_HAVE_CBSY |
> + TMIO_MMC_MIN_RCAR2,
> .capabilities = MMC_CAP_SD_HIGHSPEED | MMC_CAP_SDIO_IRQ |
> MMC_CAP_CMD23,
> .bus_shift = 2,
> diff --git a/include/linux/mfd/tmio.h b/include/linux/mfd/tmio.h
> index 18b17a39d465ed..b572955e6de6ab 100644
> --- a/include/linux/mfd/tmio.h
> +++ b/include/linux/mfd/tmio.h
> @@ -107,6 +107,9 @@
> */
> #define TMIO_MMC_CLK_ACTUAL BIT(10)
>
> +/* Some controllers have a CBSY bit */
> +#define TMIO_MMC_HAVE_CBSY BIT(11)
> +
> int tmio_core_mmc_enable(void __iomem *cnf, int shift, unsigned long base);
> int tmio_core_mmc_resume(void __iomem *cnf, int shift, unsigned long base);
> void tmio_core_mmc_pwr(void __iomem *cnf, int shift, int state);
> --
> 2.11.0
>
next prev parent reply other threads:[~2017-08-10 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 19:00 [PATCH] mmc: renesas_sdhi: use extra flag for CBSY usage Wolfram Sang
2017-08-10 7:58 ` Simon Horman [this message]
2017-08-10 8:46 ` Wolfram Sang
2017-08-14 15:00 ` Geert Uytterhoeven
2017-08-14 15:26 ` 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=20170810075850.GD16647@verge.net.au \
--to=horms@verge.net.au \
--cc=chris.brandt@renesas.com \
--cc=dirk.behme@de.bosch.com \
--cc=lee.jones@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 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.