From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mxs/dma: Enlarge the CCW descriptor area to 4 pages
Date: Fri, 14 Sep 2012 09:57:34 +0200 [thread overview]
Message-ID: <201209140957.34863.marex@denx.de> (raw)
In-Reply-To: <1347591975.1943.12.camel@vkoul-udesk3>
Dear Vinod Koul,
> On Wed, 2012-09-05 at 03:46 +0200, Marek Vasut wrote:
> > Dear Shawn Guo,
> >
> > > On Tue, Sep 04, 2012 at 06:04:25AM +0200, Marek Vasut wrote:
> > > > In case of a large SPI flash, the amount of DMA descriptors
> > > > available to the DMA driver is not large enough anymore. For
> > > > example 8MB SPI flash now needs 129 descriptors to be transfered
> > > > in one long read. There are currently 53 descriptors available in
> > > > one PAGE_SIZE-big block. Enlarge the allocated descriptor area to
> > > > four PAGE_SIZE blocks to fulfill such requirements.
> > > >
> > > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > > Cc: Dan Williams <djbw@fb.com>
> > > > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > > > Cc: Shawn Guo <shawn.guo@linaro.org>
> > >
> > > Acked-by: Shawn Guo <shawn.guo@linaro.org>
> > >
> > > Vinod (copied) is the primary maintainer and collecting dma patches
> > > now.
> >
> > Understood.
> >
> > Let me ask about another thing. If there'll eventually be some device
> > that'd need even larger transfer (say ... hundreds of megs) we'd end up
> > with trouble again.
> >
> > One way to fix this is to recycle descriptors that were already used
> > during the transfer, but can we really do it fast enough, so the DMA
> > would do it's job at one end of the descriptor chain and we'd be
> > building the other?
>
> See the comment in dma_ctrl_flags:
> * @DMA_CTRL_ACK - if clear, the descriptor cannot be reused until the
> client * acknowledges receipt, i.e. has has a chance to establish any
> dependency * chains
> Setting this would mean that driver can reuse the descriptor once the
> transaction has completed.
Sure, but then building the DMA chain on-the-fly might be a little bit too
crazy. Still, I think we're safe with using 4 pages for now, it's more than
plenty.
> > The other (easier) way is to let the device that claims the particular
> > DMA channel allocate as much descriptors as it might ever need, which I
> > think is wrong.
>
> Correct.
>
> > What do you think ?
> >
> > Best regards,
> > Marek Vasut
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-09-14 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 4:04 [PATCH] mxs/dma: Enlarge the CCW descriptor area to 4 pages Marek Vasut
2012-09-05 1:40 ` Shawn Guo
2012-09-05 1:46 ` Marek Vasut
2012-09-05 2:39 ` Shawn Guo
2012-09-05 2:57 ` Marek Vasut
2012-09-14 3:06 ` Vinod Koul
2012-09-14 7:57 ` Marek Vasut [this message]
2012-09-14 8:30 ` Russell King - ARM Linux
2012-09-14 8:56 ` Vinod Koul
2012-09-14 3:06 ` Vinod Koul
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=201209140957.34863.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.