linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jassi Brar <jassisinghbrar@gmail.com>
To: "Raju, Sundaram" <sundaram@ti.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC] dmaengine: add new api for preparing simple slave transfer
Date: Fri, 10 Jun 2011 00:28:25 +0530	[thread overview]
Message-ID: <BANLkTikvURS7aQEBax0xEfcFZMg3-cUPow@mail.gmail.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E940301FE2DED@dbde02.ent.ti.com>

On Thu, Jun 9, 2011 at 6:09 PM, Raju, Sundaram <sundaram@ti.com> wrote:

> Generic buffer description:
> A generic buffer can be split into number of frames which contain number of chunks inside them. The frames need not be contiguous, nor do the chunks inside a frame.
>
>        -------------------------------------------------------------------
>        | Chunk 0 |ICG| Chunk 1 |ICG| ... |ICG| Chunk n |       Frame 0
>        -------------------------------------------------------------------
>        |                       Inter Frame Gap                     |
>        -------------------------------------------------------------------
>        | Chunk 0 |ICG| Chunk 1 |ICG| ... |ICG| Chunk n |       Frame 1
>        -------------------------------------------------------------------
>        |                       Inter Frame Gap                     |
>        -------------------------------------------------------------------
>        |                               ........                                    |
>        -------------------------------------------------------------------
>        |                       Inter Frame Gap                     |
>        -------------------------------------------------------------------
>        | Chunk 0 |ICG| Chunk 1 |ICG| ... |ICG| Chunk n |       Frame m
>        -------------------------------------------------------------------

IIUC the above figure, the work done by DMA controller remains the
same, either by
passing this as a transfer of the new type or as a normal sg-list  - unless
the DMAC driver attempts to reorder the transfers or the DMAC h/w
natively supports
some form of sg-list.
For DMACs, that have no special support, different representation
wouldn't make a
difference.
And if the DMAC does support the kind of fancy scatter-gather, it
should be possible for
the dma api driver to analyze the submitted 'normal' sg-list and
program the transfers at one go.
Besides, it should be possible to have a 'template' sequence of
requests prepared
already because usually, for above mentioned scenario, the parameters
don't change across
items in a list.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-06-09 18:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 12:39 [RFC] dmaengine: add new api for preparing simple slave transfer Raju, Sundaram
2011-06-09 12:47 ` Russell King - ARM Linux
2011-06-09 16:01   ` Raju, Sundaram
2011-06-09 16:32     ` Russell King - ARM Linux
2011-06-10  6:13       ` Koul, Vinod
2011-06-10 10:21         ` Raju, Sundaram
2011-06-10 10:43           ` Russell King - ARM Linux
2011-06-10 11:48             ` Raju, Sundaram
2011-06-10 13:33               ` Russell King - ARM Linux
2011-06-13 14:13                 ` Linus Walleij
2011-06-14  5:38                   ` Raju, Sundaram
2011-06-14  5:59                     ` Linus Walleij
2011-06-10  6:09     ` Koul, Vinod
2011-06-10 11:13       ` Raju, Sundaram
2011-06-10 16:47         ` Koul, Vinod
2011-06-14  6:42           ` Raju, Sundaram
2011-06-16  5:45             ` Koul, Vinod
2011-07-07 12:15               ` Raju, Sundaram
2011-07-07 19:37                 ` Linus Walleij
2011-06-09 18:58 ` Jassi Brar [this message]

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=BANLkTikvURS7aQEBax0xEfcFZMg3-cUPow@mail.gmail.com \
    --to=jassisinghbrar@gmail.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sundaram@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).