From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Franklin S Cooper Jr <fcooper@ti.com>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
tony@atomide.com, rogerq@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] mtd: nand: omap2: Fix SDMA support for NAND DMA prefetch
Date: Fri, 22 Apr 2016 11:12:43 +0200 [thread overview]
Message-ID: <20160422111243.68de7cb0@bbrezillon> (raw)
In-Reply-To: <1460752139-12742-1-git-send-email-fcooper@ti.com>
On Fri, 15 Apr 2016 15:28:57 -0500
Franklin S Cooper Jr <fcooper@ti.com> wrote:
> NAND DMA prefetch for SDMA based devices has been broken for awhile. This
> patchset fixes it so SOCs that use the SDMA can make use of the NAND
> DMA prefetch.
>
> I've decided to split this patchset from the slightly larger patchset that
> included EDMA support. Adding EDMA support will be added in a later
> patchset.
>
> Tested using the latest master on:
> am37 gp evm
>
> Due to a silicon issue Dra7 SoCs are unable to use NAND DMA prefetch.
Applied, thanks.
Boris
>
> Cooper Jr., Franklin (2):
> mtd: nand: omap2: Start dma request before enabling prefetch
> mtd: nand: omap2: Fix high memory dma prefetch transfer
>
> drivers/mtd/nand/omap2.c | 22 +++++++---------------
> 1 file changed, 7 insertions(+), 15 deletions(-)
>
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-04-22 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 20:28 [PATCH 0/2] mtd: nand: omap2: Fix SDMA support for NAND DMA prefetch Franklin S Cooper Jr
2016-04-15 20:28 ` [PATCH 1/2] mtd: nand: omap2: Start dma request before enabling prefetch Franklin S Cooper Jr
2016-04-15 20:28 ` [PATCH 2/2] mtd: nand: omap2: Fix high memory dma prefetch transfer Franklin S Cooper Jr
2016-04-22 9:12 ` Boris Brezillon [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=20160422111243.68de7cb0@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fcooper@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=tony@atomide.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).