All of lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Song <21cnbao@gmail.com>
To: Jassi Brar <jaswinder.singh@linaro.org>
Cc: dan.j.williams@intel.com, sundaram@ti.com,
	linus.walleij@linaro.org, vinod.koul@intel.com,
	rmk+kernel@arm.linux.org.uk, linux-omap@vger.kernel.org,
	DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>
Subject: Re: [PATCH] DMAEngine: Define generic transfer request api
Date: Tue, 13 Sep 2011 09:21:54 +0800	[thread overview]
Message-ID: <CAGsJ_4xaDyQgtGZwDjnXn-=ouHzqmVfwaKeDxuouvkPHMkr8mw@mail.gmail.com> (raw)
In-Reply-To: <CAJe_ZhcxEaHoj+6+mTKOk2Jz9KBeTP-M3c2VMn=S4Y-K6iegKw@mail.gmail.com>

2011/9/13 Jassi Brar <jaswinder.singh@linaro.org>:
> On 12 September 2011 21:56, Barry Song <21cnbao@gmail.com> wrote:
>>> Define a new api that could be used for doing fancy data transfers
>>> like interleaved to contiguous copy and vice-versa.
>>> Traditional SG_list based transfers tend to be very inefficient in
>>> such cases as where the interleave and chunk are only a few bytes,
>>> which call for a very condensed api to convey pattern of the transfer.
>>>
>>> This api supports all 4 variants of scatter-gather and contiguous transfer.
>>> Besides, it could also represent common operations like
>>>        device_prep_dma_{cyclic, memset, memcpy}
>>> and maybe some more that I am not sure of.
>>>
>>> Of course, neither can this api help transfers that don't lend to DMA by
>>> nature, i.e, scattered tiny read/writes with no periodic pattern.
>>>
>>> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
>>
>> anyway, this API needs a real user to prove why it needs to exist.
>>
>> prima2 can be the 1st(?, 2nd if TI uses) user of this API. let's try
>> to see what the driver will be with this api. Then we might figure out
>> more about what it should be.
>>
> Did you discover any issue with the api?

no until now, but i need to test as i said since there is nobody else
has used it before. so i just hold the formal ACK for a moment.

> Because only three days ago you said
> {
> Jassi, you might think my reply as an ACK to "[PATCH] DMAEngine:
> Define generic transfer request api".
> }

if test pass, to the patch, and even for the moment, to the API's idea
Acked-by: Barry Song <baohua.song@csr.com>

>
> The api met your requirements easily not because I know them already,
> but because I designed the api to be as generic as practically possible.
>

-barry
--
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

  reply	other threads:[~2011-09-13  1:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGsJ_4wXURUwbf-fcNOq1m5-NJ9+VMuDq+9OJpBjFZK4C_X3cw@mail.gmail.com>
2011-09-12 16:26 ` [PATCH] DMAEngine: Define generic transfer request api Barry Song
2011-09-12 16:54   ` Jassi Brar
2011-09-13  1:21     ` Barry Song [this message]
2011-09-13  7:46       ` Barry Song
2011-09-13  8:43         ` Jassi Brar
2011-09-13  8:58           ` Barry Song
2011-09-15  6:31             ` Barry Song
2011-09-15  6:43               ` Jassi Brar
2011-09-15  6:49                 ` Barry Song
2011-09-15  8:17                 ` Barry Song
2011-08-12 11:14 Jassi Brar
2011-08-16 12:56 ` Koul, Vinod
2011-08-16 13:06   ` Linus Walleij
2011-08-19 13:43     ` Koul, Vinod
2011-08-19 14:19       ` Linus Walleij
2011-08-19 15:46         ` Jassi Brar
2011-08-19 17:28           ` Koul, Vinod
2011-08-19 18:45             ` Jassi Brar
2011-08-23 14:43       ` Matt Porter
2011-08-23 14:43         ` Matt Porter
2011-08-16 14:32   ` Jassi Brar

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='CAGsJ_4xaDyQgtGZwDjnXn-=ouHzqmVfwaKeDxuouvkPHMkr8mw@mail.gmail.com' \
    --to=21cnbao@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=sundaram@ti.com \
    --cc=vinod.koul@intel.com \
    --cc=workgroup.linux@csr.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.