From: Ladislav Michl <ladis@linux-mips.org>
To: Roger Quadros <rogerq@ti.com>
Cc: linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
Tony Lindgren <tony@atomide.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: Fri, 10 Nov 2017 10:51:54 +0100 [thread overview]
Message-ID: <20171110095154.kf34cd7h2eyfvwf3@lenoch> (raw)
In-Reply-To: <4a58dfac-8cc9-101f-b079-da8925d7ab4c@ti.com>
On Fri, Nov 10, 2017 at 10:21:51AM +0200, Roger Quadros wrote:
> On 09/11/17 11:15, Ladislav Michl wrote:
> > Since the very first commit (36cd4fb5d277: "[MTD] [OneNAND] Add OMAP2 / OMAP3
> > OneNAND driver") DMA is disabled for OMAP2. Later fixes thus went only into
> > OMAP3 specific DMA functions which turned out not to be so OMAP3 specific.
> > Therefore replace open coded timeout waiting for completion in OMAP3
> > functions with API call and merge those two implementations.
> >
> > Note that currently the is no single DMA user, so this change is basically
> > no-op. Those interested will have to find DMA configuration in the
> > linux-omap.git history.
> >
> > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
>
> I'll be happy if there are no OMAP2 vs OMAP3 differences in code but we need to
> be absolutely sure that we don't break DMA functionality if it ever worked.
It probably worked at least for OMAP3 as it was enabled in legacy kernels.
> Can we somehow test OneNAND DMA on OMAP2 and OMAP3?
> Tony?
I'll prepare next version patch serie for easier testing. Of course I would
prefer to be able to test changes myself, but I do not have any Nokias :-)
ladis
next prev parent reply other threads:[~2017-11-10 9:52 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 [this message]
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
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=20171110095154.kf34cd7h2eyfvwf3@lenoch \
--to=ladis@linux-mips.org \
--cc=boris.brezillon@free-electrons.com \
--cc=kyungmin.park@samsung.com \
--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).