From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH 3/3] mmc: renesas_sdhi_internal_dmac: use multiple segments if possible
Date: Tue, 7 May 2019 07:27:40 +0000 [thread overview]
Message-ID: <OSBPR01MB3174C6DEEFD26C21765B1786D8310@OSBPR01MB3174.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190426093711.GC1031@kunai>
Hi Wolfram-san,
> From: Wolfram Sang, Sent: Friday, April 26, 2019 6:37 PM
>
>
> > +static void
> > +renesas_sdhi_internal_dmac_init_card(struct tmio_mmc_host *host,
> > + struct mmc_card *card)
> > +{
> > + if (host->pdev->dev.iommu_group &&
> > + (mmc_card_mmc(card) || mmc_card_sd(card)))
> > + host->mmc->max_segs = 512;
> > + else
> > + host->mmc->max_segs = host->pdata->max_segs;
> > +}
> > +
>
> Will this work with Gen2 as well if we explicitly set max_segs in
> of_rcar_gen2_compatible (renesas_sdhi_sys_dmac.c)?
Yes, Gen2 (renesas_sdhi_sys_dmac.c) can work with max_segs = 512.
# Enabling IPMMU on Gen2 might cause some troubles anyway regardless the max_segs value though.
> Then we could simply
> move the above chunk to renesas_sdhi_core.c and use this minimal diff.
>
> --- a/drivers/mmc/host/renesas_sdhi_core.c
> +++ b/drivers/mmc/host/renesas_sdhi_core.c
> @@ -726,6 +726,8 @@ int renesas_sdhi_probe(struct platform_device *pdev,
>
> /* SDR speeds are only available on Gen2+ */
> if (mmc_data->flags & TMIO_MMC_MIN_RCAR2) {
> + host->ops.init_card = renesas_sdhi_init_card;
> +
> /* card_busy caused issues on r8a73a4 (pre-Gen2) CD-less SDHI */
> host->ops.card_busy = renesas_sdhi_card_busy;
> host->ops.start_signal_voltage_switch =
>
> What do you think, Shimoda-san?
I think it's a nice idea. So, I'll modify this patch on v2.
Best regards,
Yoshihiro Shimoda
next prev parent reply other threads:[~2019-05-07 7:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 5:18 [PATCH 0/3] mmc: renesas_sdhi_internal_dmac: improve performance by using IOMMU Yoshihiro Shimoda
2019-04-26 5:18 ` [PATCH 1/3] mmc: tmio: add init_card ops Yoshihiro Shimoda
2019-04-26 9:15 ` Wolfram Sang
2019-04-26 9:45 ` Simon Horman
2019-04-26 9:56 ` Wolfram Sang
2019-04-26 10:17 ` Simon Horman
2019-04-26 5:18 ` [PATCH 2/3] mmc: tmio: No memory size limitation if runs on IOMMU Yoshihiro Shimoda
2019-04-26 8:09 ` Sergei Shtylyov
2019-04-26 9:17 ` Wolfram Sang
2019-05-07 7:13 ` Yoshihiro Shimoda
2019-04-26 9:45 ` Simon Horman
2019-04-26 5:18 ` [PATCH 3/3] mmc: renesas_sdhi_internal_dmac: use multiple segments if possible Yoshihiro Shimoda
2019-04-26 9:37 ` Wolfram Sang
2019-05-07 7:27 ` Yoshihiro Shimoda [this message]
2019-04-26 9:45 ` Simon Horman
2019-04-26 9:46 ` [PATCH 0/3] mmc: renesas_sdhi_internal_dmac: improve performance by using IOMMU Wolfram Sang
2019-05-07 8:58 ` Yoshihiro Shimoda
2019-05-08 4:28 ` Yoshihiro Shimoda
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=OSBPR01MB3174C6DEEFD26C21765B1786D8310@OSBPR01MB3174.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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 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).