From: Tony Lindgren <tony@atomide.com>
To: "Franklin S Cooper Jr." <fcooper@ti.com>
Cc: Roger Quadros <rogerq@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
nsekhar@ti.com, computersforpeace@gmail.com, dwmw2@infradead.org
Subject: Re: [PATCH 1/5] mtd: nand: omap2: Support parsing dma channel information from DT
Date: Wed, 14 Oct 2015 11:13:38 -0700 [thread overview]
Message-ID: <20151014181337.GF10113@atomide.com> (raw)
In-Reply-To: <561E8184.6020206@ti.com>
* Franklin S Cooper Jr. <fcooper@ti.com> [151014 09:27]:
>
>
> On 10/14/2015 11:18 AM, Tony Lindgren wrote:
> > * Franklin S Cooper Jr. <fcooper@ti.com> [151014 07:37]:
> >>
> >> On 10/14/2015 09:11 AM, Roger Quadros wrote:
> >>> On 14/10/15 16:26, Franklin S Cooper Jr. wrote:
> >>>> On 10/14/2015 06:52 AM, Roger Quadros wrote:
> >>>>> Franklin,
> >>>>>
> >>>>> On 14/10/15 14:36, Roger Quadros wrote:
> >>>>>> On 13/10/15 04:38, Franklin S Cooper Jr wrote:
> >>>>>>> Switch from dma_request_channel to allow passing dma channel
> >>>>>>> information from DT rather than hardcoding a value.
> >>>>>>>
> >>>>>>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> >>>>>> Acked-by: Roger Quadros <rogerq@ti.com>
> >>>>>>
> >>>>>>> ---
> >>>>>>> drivers/mtd/nand/omap2.c | 4 +++-
> >>>>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
> >>>>>>>
> >>>>>>> diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
> >>>>>>> index d0f2620..957c32f 100644
> >>>>>>> --- a/drivers/mtd/nand/omap2.c
> >>>>>>> +++ b/drivers/mtd/nand/omap2.c
> >>>>>>> @@ -1866,7 +1866,9 @@ static int omap_nand_probe(struct platform_device *pdev)
> >>>>>>> dma_cap_zero(mask);
> >>>>>>> dma_cap_set(DMA_SLAVE, mask);
> >>>>>>> sig = OMAP24XX_DMA_GPMC;
> >>>>>>> - info->dma = dma_request_channel(mask, omap_dma_filter_fn, &sig);
> >>>>>>> + info->dma = dma_request_slave_channel_compat(mask,
> >>>>>>> + omap_dma_filter_fn, &sig, pdev->dev.parent, "rxtx");
> >>>>>>> +
> >>>>> Just discovered that you are using the parent device node.
> >>>>>
> >>>>> How about moving the dma bindings to the nand node instead and using
> >>>>> pdev->dev here?
> >>>> Roger,
> >>>>
> >>>> From what I can tell the interrupt number and the dma channel will always be
> >>>> the same no matter what. Doesn't matter if you have multiple nands or a
> >>>> combination of nands and nors. Since that is the case I think it just makes
> >>>> sense to leave it in the gpmc parent node and define it once.
> >>> Is prefetch/writepost dma used for NOR or any other GPMC peripheral
> >>> or only for NAND?
> >> The dma seems tied to the prefetch. From what I can tell the prefetch is only
> >> used by nand.
> >>> Let's also get Tony's inputs on this.
> >> Sure.
> > Hmm so what would keep other devices from using the prefetch
> Looking at the TRM any references to the prefetch are always with respect to
> NAND.
>
> I also see the below mentioned in the TRM.
> Pre-fetch and write posting engine associated with system DMA to get full performance from NAND
> device with minimum impact on NOR/SRAM concurrent access.
OK up to you guys to figure out if it may be usable in a generic way then :)
Regards,
Tony
next prev parent reply other threads:[~2015-10-14 18:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 1:38 [PATCH 0/5] mtd: nand: Fix support for NAND DMA Prefetch Franklin S Cooper Jr
2015-10-13 1:38 ` [PATCH 1/5] mtd: nand: omap2: Support parsing dma channel information from DT Franklin S Cooper Jr
2015-10-14 11:36 ` Roger Quadros
2015-10-14 11:52 ` Roger Quadros
2015-10-14 13:26 ` Franklin S Cooper Jr.
2015-10-14 14:11 ` Roger Quadros
[not found] ` <561E629F.5070202-l0cyMroinI0@public.gmane.org>
2015-10-14 14:32 ` Franklin S Cooper Jr.
[not found] ` <561E6791.3030404-l0cyMroinI0@public.gmane.org>
2015-10-14 16:18 ` Tony Lindgren
[not found] ` <20151014161813.GC10113-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-10-14 16:23 ` Franklin S Cooper Jr.
2015-10-14 18:13 ` Tony Lindgren [this message]
[not found] ` <20151014181337.GF10113-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-10-14 20:03 ` Franklin S Cooper Jr.
2015-10-15 7:35 ` Roger Quadros
2015-10-15 17:12 ` Franklin S Cooper Jr.
2015-10-13 1:38 ` [PATCH 2/5] mtd: nand: omap2: Start dma request before enabling prefetch Franklin S Cooper Jr
2015-10-14 11:41 ` Roger Quadros
[not found] ` <561E3F5B.6040102-l0cyMroinI0@public.gmane.org>
2015-10-14 13:45 ` Franklin S Cooper Jr.
2015-10-13 1:38 ` [PATCH 3/5] mtd: nand: omap2: Fix high memory dma prefetch transfer Franklin S Cooper Jr
2015-10-13 1:38 ` [PATCH 4/5] ARM: dts: am437x/am33xx/omap3/dm816x: Add gpmc dma channel Franklin S Cooper Jr
2015-10-14 11:44 ` Roger Quadros
2015-10-14 13:57 ` Franklin S Cooper Jr.
2015-10-13 1:38 ` [PATCH 5/5] ARM: OMAP2+: Update gpmc and nand DT binding documentation Franklin S Cooper Jr
2015-10-14 11:50 ` Roger Quadros
2015-10-15 17:14 ` Franklin S Cooper Jr.
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=20151014181337.GF10113@atomide.com \
--to=tony@atomide.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--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=nsekhar@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).