From: Ladislav Michl <ladis@linux-mips.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH v3 5/7] mtd: onenand: omap2: Unify OMAP2 and OMAP3 DMA implementation
Date: Fri, 10 Nov 2017 19:26:21 +0100 [thread overview]
Message-ID: <20171110182621.ntiptm3h2u437nv7@lenoch> (raw)
In-Reply-To: <20171110152423.GM28152@atomide.com>
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.
Hmm, that's probably what comment in omap3-n900.dts is saying:
"sys_ndmareq1 could be used by the driver, not as gpio65 though"
However board-rx51 (is that n900?) is using it as gpio pin.
Also omap2420-n8x0-common.dtsi comment says: "gpio-irq for dma: 26"
and it matches board-n8x0.c platform data configuration.
But I still missing pinmux configuration as we need to add it into
DT as well. I guess this was originally done in bootloader. Any hint
where can I get this info from?
Thanks,
ladis
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Ladislav Michl <ladis@linux-mips.org>
To: Tony Lindgren <tony@atomide.com>
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: Fri, 10 Nov 2017 19:26:21 +0100 [thread overview]
Message-ID: <20171110182621.ntiptm3h2u437nv7@lenoch> (raw)
In-Reply-To: <20171110152423.GM28152@atomide.com>
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.
Hmm, that's probably what comment in omap3-n900.dts is saying:
"sys_ndmareq1 could be used by the driver, not as gpio65 though"
However board-rx51 (is that n900?) is using it as gpio pin.
Also omap2420-n8x0-common.dtsi comment says: "gpio-irq for dma: 26"
and it matches board-n8x0.c platform data configuration.
But I still missing pinmux configuration as we need to add it into
DT as well. I guess this was originally done in bootloader. Any hint
where can I get this info from?
Thanks,
ladis
next prev parent reply other threads:[~2017-11-10 18:26 UTC|newest]
Thread overview: 92+ 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:11 ` Ladislav Michl
2017-11-09 9:12 ` [PATCH v3 1/7] memory: omap-gpmc: Refactor OneNAND support Ladislav Michl
2017-11-09 9:12 ` Ladislav Michl
2017-11-09 17:56 ` Tony Lindgren
2017-11-09 17:56 ` Tony Lindgren
2017-11-09 18:10 ` Ladislav Michl
2017-11-09 18:10 ` Ladislav Michl
2017-11-09 18:26 ` Tony Lindgren
2017-11-09 18:26 ` Tony Lindgren
2017-11-09 18:34 ` Ladislav Michl
2017-11-09 18:34 ` Ladislav Michl
2017-11-09 18:48 ` Tony Lindgren
2017-11-09 18:48 ` Tony Lindgren
2017-11-09 19:10 ` Ladislav Michl
2017-11-09 19:10 ` Ladislav Michl
2017-11-09 21:59 ` Tony Lindgren
2017-11-09 21:59 ` Tony Lindgren
2017-11-09 22:26 ` Ladislav Michl
2017-11-09 22:26 ` Ladislav Michl
2017-11-10 8:12 ` Roger Quadros
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-09 9:13 ` Ladislav Michl
2017-11-10 8:17 ` Roger Quadros
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-09 9:14 ` Ladislav Michl
2017-11-10 8:18 ` Roger Quadros
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-09 9:14 ` Ladislav Michl
2017-11-10 8:19 ` Roger Quadros
2017-11-10 8:19 ` Roger Quadros
2017-11-10 9:48 ` Ladislav Michl
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-09 9:15 ` Ladislav Michl
2017-11-10 8:21 ` Roger Quadros
2017-11-10 8:21 ` Roger Quadros
2017-11-10 9:51 ` Ladislav Michl
2017-11-10 9:51 ` Ladislav Michl
2017-11-10 15:26 ` Tony Lindgren
2017-11-10 15:26 ` Tony Lindgren
2017-11-10 18:19 ` Ladislav Michl
2017-11-10 18:19 ` Ladislav Michl
2017-11-10 18:29 ` Tony Lindgren
2017-11-10 18:29 ` Tony Lindgren
2017-11-11 12:50 ` Ladislav Michl
2017-11-11 12:50 ` Ladislav Michl
2017-11-13 20:10 ` Peter Ujfalusi
2017-11-13 20:10 ` Peter Ujfalusi
2017-11-14 14:47 ` Roger Quadros
2017-11-14 14:47 ` Roger Quadros
2017-11-14 15:03 ` Ladislav Michl
2017-11-14 15:03 ` Ladislav Michl
2017-11-10 8:25 ` Peter Ujfalusi
2017-11-10 8:25 ` Peter Ujfalusi
2017-11-10 10:04 ` Ladislav Michl
2017-11-10 10:04 ` Ladislav Michl
2017-11-10 15:24 ` Tony Lindgren
2017-11-10 15:24 ` Tony Lindgren
2017-11-10 18:26 ` Ladislav Michl [this message]
2017-11-10 18:26 ` Ladislav Michl
2017-11-10 18:48 ` Tony Lindgren
2017-11-10 18:48 ` Tony Lindgren
2017-11-10 21:39 ` Ladislav Michl
2017-11-10 21:39 ` Ladislav Michl
2017-11-14 21:53 ` Tony Lindgren
2017-11-14 21:53 ` Tony Lindgren
2017-11-14 22:32 ` Ladislav Michl
2017-11-14 22:32 ` Ladislav Michl
2017-11-15 2:11 ` Tony Lindgren
2017-11-15 2:11 ` Tony Lindgren
2017-11-13 8:22 ` Peter Ujfalusi
2017-11-13 8:22 ` Peter Ujfalusi
2017-11-13 12:15 ` Ladislav Michl
2017-11-13 12:15 ` Ladislav Michl
2017-11-13 14:36 ` Peter Ujfalusi
2017-11-13 14:36 ` Peter Ujfalusi
2017-11-13 15:23 ` Tony Lindgren
2017-11-13 15:23 ` Tony Lindgren
2017-11-13 15:27 ` Ladislav Michl
2017-11-13 15:27 ` Ladislav Michl
2017-11-14 15:05 ` Roger Quadros
2017-11-14 15:05 ` Roger Quadros
2017-11-14 15:22 ` Ladislav Michl
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:16 ` Ladislav Michl
2017-11-09 9:17 ` [PATCH v3 7/7] mtd: onenand: omap2: Configure driver from DT Ladislav Michl
2017-11-09 9:17 ` 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=20171110182621.ntiptm3h2u437nv7@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=peter.ujfalusi@ti.com \
--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 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.