linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, ian@mnementh.co.uk, cjb@laptop.org,
	linux-sh@vger.kernel.org, max.filippov@cogentembedded.com
Subject: Re: [PATCH] tmio_mmc_dma: fix PIO fallback on SDHI
Date: Fri, 02 Aug 2013 18:10:21 +0000	[thread overview]
Message-ID: <51FBF60D.1040309@cogentembedded.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1308021332260.28012@axis700.grange>

On 08/02/2013 03:35 PM, Guennadi Liakhovetski wrote:

>> I'm testing SH-Mobile SDHI driver in DMA mode with a  new DMA controller  using
>> 'bonnie++' and getting DMA error after which the tmio_mmc_dma.c code falls back
>> to PIO but all commands time out after that.  It turned out that the fallback
>> code calls tmio_mmc_enable_dma() with RX/TX channels already freed and pointers
>> to them cleared, so that the function bails out early instead  of clearing the
>> DMA bit in the CTL_DMA_ENABLE register.  Fixing the RX/TX channel check so that
>> it takes place only when enabling DMA helps with the PIO fallback.

>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

>> ---
>> The patch is against Chris Ball's 'mmc.git' repo, 'master' branch.

>>   drivers/mmc/host/tmio_mmc_dma.c |    2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)

>> Index: mmc/drivers/mmc/host/tmio_mmc_dma.c
>> =================================>> --- mmc.orig/drivers/mmc/host/tmio_mmc_dma.c
>> +++ mmc/drivers/mmc/host/tmio_mmc_dma.c
>> @@ -25,7 +25,7 @@
>>
>>   void tmio_mmc_enable_dma(struct tmio_mmc_host *host, bool enable)
>>   {
>> -	if (!host->chan_tx || !host->chan_rx)
>> +	if (enable && !(host->chan_tx && host->chan_rx))
>>   		return;

> Ok, I see the problem and this does fix it. But it adds complexity to the
> driver - one more condition to an if.

    So what?

> Whereas, I think, it can be avoided if we just move calls to

> tmio_mmc_enable_dma(host, false);

> in tmio_mmc_start_dma_rx() and tmio_mmc_start_dma_tx() a couple of lines

    Well, not couple. :-P

> up - before clearing ->chan_rx and ->chan_tx pointers? That should work
> too at no cost.

    Well, it was my first variant. However, not knowing the hardware well, I 
deemed it not quite safe to clear the DMA bit before shutting down the DMA 
channels, so came up with the second version (which I consider more logically 
correct).

> I think that would be a better fix, could you, please, try?

    I tried it but mystically fixing the PIO fallback makes DMA error less 
frequent. IIRC, I didn't see DMA error with the first variant of the fix, so 
I'll have to retry it...

> Thanks
> Guennadi

WBR, Sergei


      reply	other threads:[~2013-08-02 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 21:17 [PATCH] tmio_mmc_dma: fix PIO fallback on SDHI Sergei Shtylyov
2013-08-01 21:26 ` Sergei Shtylyov
2013-08-02 11:35 ` Guennadi Liakhovetski
2013-08-02 18:10   ` Sergei Shtylyov [this message]

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=51FBF60D.1040309@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=cjb@laptop.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=ian@mnementh.co.uk \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=max.filippov@cogentembedded.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).