From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-mmc@vger.kernel.org, g.liakhovetski@gmx.de,
ian@mnementh.co.uk, cjb@laptop.org
Cc: linux-sh@vger.kernel.org, max.filippov@cogentembedded.com
Subject: Re: [PATCH v2] tmio_mmc_dma: fix PIO fallback on SDHI
Date: Fri, 09 Aug 2013 22:32:12 +0400 [thread overview]
Message-ID: <520535AC.6000200@cogentembedded.com> (raw)
In-Reply-To: <201308030233.29446.sergei.shtylyov@cogentembedded.com>
Hello.
On 08/03/2013 02:33 AM, Sergei Shtylyov wrote:
> I'm testing SH-Mobile SDHI driver in DMA mode with a new DMA controller using
The driver for this controller is using drivers/dma/sh/shdma-base.c framework.
> 'bonnie++' and getting DMA error
And I suspect some bug/race in shdma-base.c. The S/G request that fails
seems to always consist of 32 segments (maximum for shdma-base.c) and it fails
like this:
hpb-dma-engine hpb-dma-engine: No free link descriptor available
which is a message that shdma_add_desc() prints when shdma_get-desc() returns
NULL. When I turn on all dev_dbg() calls (via #define DEBUG) in shdma-base.c.
the error is *gone*...
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org # 3.1+
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-mmc@vger.kernel.org, g.liakhovetski@gmx.de,
ian@mnementh.co.uk, cjb@laptop.org
Cc: linux-sh@vger.kernel.org, max.filippov@cogentembedded.com
Subject: Re: [PATCH v2] tmio_mmc_dma: fix PIO fallback on SDHI
Date: Fri, 09 Aug 2013 18:32:12 +0000 [thread overview]
Message-ID: <520535AC.6000200@cogentembedded.com> (raw)
In-Reply-To: <201308030233.29446.sergei.shtylyov@cogentembedded.com>
Hello.
On 08/03/2013 02:33 AM, Sergei Shtylyov wrote:
> I'm testing SH-Mobile SDHI driver in DMA mode with a new DMA controller using
The driver for this controller is using drivers/dma/sh/shdma-base.c framework.
> 'bonnie++' and getting DMA error
And I suspect some bug/race in shdma-base.c. The S/G request that fails
seems to always consist of 32 segments (maximum for shdma-base.c) and it fails
like this:
hpb-dma-engine hpb-dma-engine: No free link descriptor available
which is a message that shdma_add_desc() prints when shdma_get-desc() returns
NULL. When I turn on all dev_dbg() calls (via #define DEBUG) in shdma-base.c.
the error is *gone*...
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Cc: stable@vger.kernel.org # 3.1+
WBR, Sergei
next prev parent reply other threads:[~2013-08-09 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 22:33 [PATCH v2] tmio_mmc_dma: fix PIO fallback on SDHI Sergei Shtylyov
2013-08-02 22:33 ` Sergei Shtylyov
2013-08-03 22:36 ` Guennadi Liakhovetski
2013-08-03 22:36 ` Guennadi Liakhovetski
2013-08-04 14:10 ` Sergei Shtylyov
2013-08-04 14:10 ` Sergei Shtylyov
2013-08-05 22:37 ` Sergei Shtylyov
2013-08-05 22:37 ` Sergei Shtylyov
2013-08-09 18:41 ` Sergei Shtylyov
2013-08-09 18:41 ` Sergei Shtylyov
2013-08-25 3:39 ` Chris Ball
2013-08-25 3:39 ` Chris Ball
2013-08-09 18:32 ` Sergei Shtylyov [this message]
2013-08-09 18:32 ` Sergei Shtylyov
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=520535AC.6000200@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 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.