From: Tony Lindgren <tony@atomide.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
Roger Quadros <rogerq@ti.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v3 5/7] mtd: onenand: omap2: Unify OMAP2 and OMAP3 DMA implementation
Date: Tue, 14 Nov 2017 13:53:12 -0800 [thread overview]
Message-ID: <20171114215312.GI28152@atomide.com> (raw)
In-Reply-To: <20171110213918.pqq3ghblqhp2jwf2@lenoch>
* Ladislav Michl <ladis@linux-mips.org> [171110 21:41]:
> On Fri, Nov 10, 2017 at 07:24:23AM -0800, Tony Lindgren wrote:
> > FYI, the gpio pin for onenand should not be in gpio mode. It should
> > be used as external dma request line to automatically trigger new
> > transfers like we do for tusb6010 dma. But of course it's possible
> > that onenand has other issues too preventing the dma usage.
>
> Now, after reading dma and interrupt related code again, I still do
> not see how the driver could be using hardware synchronized transfer.
> DMA seems to be used as a memcpy and gpio pin a ready/busy.
> Care to elaborate a bit more?
Well take a look at mux options for the onenand connected pins,
and if there is one that has a mux option for ext_dmareq or similar,
chances are it can be used to retrigger dma transfers.
I could be wrong of course, and it could be it won't even work with
onenand.
Something to look later on for sure if anybody is interested.
Regards,
Tony
next prev parent reply other threads:[~2017-11-14 21:53 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:11 [PATCH v3 0/7] OMAP2+ OneNAND driver update Ladislav Michl
2017-11-09 9:12 ` [PATCH v3 1/7] memory: omap-gpmc: Refactor OneNAND support Ladislav Michl
2017-11-09 17:56 ` Tony Lindgren
2017-11-09 18:10 ` Ladislav Michl
2017-11-09 18:26 ` Tony Lindgren
2017-11-09 18:34 ` Ladislav Michl
2017-11-09 18:48 ` Tony Lindgren
2017-11-09 19:10 ` Ladislav Michl
2017-11-09 21:59 ` Tony Lindgren
2017-11-09 22:26 ` Ladislav Michl
2017-11-10 8:12 ` Roger Quadros
2017-11-09 9:13 ` [PATCH v3 2/7] mtd: onenand: omap2: Remove regulator support Ladislav Michl
2017-11-10 8:17 ` Roger Quadros
2017-11-09 9:14 ` [PATCH v3 3/7] mtd: onenand: omap2: Remove skip initial unlocking support Ladislav Michl
2017-11-10 8:18 ` Roger Quadros
2017-11-09 9:14 ` [PATCH v3 4/7] mtd: onenand: omap2: Remove partitioning support from platform data Ladislav Michl
2017-11-10 8:19 ` Roger Quadros
2017-11-10 9:48 ` Ladislav Michl
2017-11-09 9:15 ` [PATCH v3 5/7] mtd: onenand: omap2: Unify OMAP2 and OMAP3 DMA implementation Ladislav Michl
2017-11-10 8:21 ` Roger Quadros
2017-11-10 9:51 ` Ladislav Michl
2017-11-10 15:26 ` Tony Lindgren
2017-11-10 18:19 ` Ladislav Michl
2017-11-10 18:29 ` Tony Lindgren
2017-11-11 12:50 ` Ladislav Michl
2017-11-13 20:10 ` Peter Ujfalusi
2017-11-14 14:47 ` Roger Quadros
2017-11-14 15:03 ` Ladislav Michl
2017-11-10 8:25 ` Peter Ujfalusi
2017-11-10 10:04 ` Ladislav Michl
2017-11-10 15:24 ` Tony Lindgren
2017-11-10 18:26 ` Ladislav Michl
2017-11-10 18:48 ` Tony Lindgren
2017-11-10 21:39 ` Ladislav Michl
2017-11-14 21:53 ` Tony Lindgren [this message]
2017-11-14 22:32 ` Ladislav Michl
2017-11-15 2:11 ` Tony Lindgren
2017-11-13 8:22 ` Peter Ujfalusi
2017-11-13 12:15 ` Ladislav Michl
2017-11-13 14:36 ` Peter Ujfalusi
2017-11-13 15:23 ` Tony Lindgren
2017-11-13 15:27 ` Ladislav Michl
2017-11-14 15:05 ` Roger Quadros
2017-11-14 15:22 ` Ladislav Michl
2017-11-09 9:16 ` [PATCH v3 6/7] mtd: onenand: omap2: Do not make delay for GPIO OMAP3 specific Ladislav Michl
2017-11-09 9:17 ` [PATCH v3 7/7] mtd: onenand: omap2: Configure driver from DT Ladislav Michl
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=20171114215312.GI28152@atomide.com \
--to=tony@atomide.com \
--cc=boris.brezillon@free-electrons.com \
--cc=kyungmin.park@samsung.com \
--cc=ladis@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=rogerq@ti.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).