From: "Per Förlin" <per.friden@stericsson.com>
To: "Ira W. Snyder" <iws@ovro.caltech.edu>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFCv2 1/2] dmaengine: add support for scatterlist to scatterlist transfers
Date: Tue, 28 Sep 2010 09:13:35 +0200 [thread overview]
Message-ID: <4CA1959F.8050806@stericsson.com> (raw)
In-Reply-To: <20100927172356.GA805@ovro.caltech.edu>
> On Mon, Sep 27, 2010 at 05:23:34PM +0200, Linus Walleij wrote:
>> 2010/9/25 Ira W. Snyder <iws@ovro.caltech.edu>:
>>
>>> This adds support for scatterlist to scatterlist DMA transfers.
>>
>> This is a good idea, we have a local function to do this in DMA40 already,
>> stedma40_memcpy_sg().
>>
>
> I think that having two devices that want to implement this
> functionality as part of the DMAEngine API is a good argument for making
> it available as part of the core API. I think it would be good to add
> this to struct dma_device, and add a capability (DMA_SG?) for it as
> well.
>
> I have looked at the stedma40_memcpy_sg() function, and I think we would
> want to extend it slightly for the generic API. Is there any good reason
> to prohibit scatterlists with different numbers of elements?
No
/Per
WARNING: multiple messages have this Message-ID (diff)
From: "Per Förlin" <per.friden@stericsson.com>
To: "Ira W. Snyder" <iws@ovro.caltech.edu>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH RFCv2 1/2] dmaengine: add support for scatterlist to scatterlist transfers
Date: Tue, 28 Sep 2010 09:13:35 +0200 [thread overview]
Message-ID: <4CA1959F.8050806@stericsson.com> (raw)
In-Reply-To: <20100927172356.GA805@ovro.caltech.edu>
> On Mon, Sep 27, 2010 at 05:23:34PM +0200, Linus Walleij wrote:
>> 2010/9/25 Ira W. Snyder <iws@ovro.caltech.edu>:
>>
>>> This adds support for scatterlist to scatterlist DMA transfers.
>>
>> This is a good idea, we have a local function to do this in DMA40 already,
>> stedma40_memcpy_sg().
>>
>
> I think that having two devices that want to implement this
> functionality as part of the DMAEngine API is a good argument for making
> it available as part of the core API. I think it would be good to add
> this to struct dma_device, and add a capability (DMA_SG?) for it as
> well.
>
> I have looked at the stedma40_memcpy_sg() function, and I think we would
> want to extend it slightly for the generic API. Is there any good reason
> to prohibit scatterlists with different numbers of elements?
No
/Per
next prev parent reply other threads:[~2010-09-28 7:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 23:13 [PATCH RFCv2 0/2] dma: add support for sg-to-sg transfers Ira W. Snyder
2010-09-24 23:13 ` [PATCH RFCv2 1/2] dmaengine: add support for scatterlist to scatterlist transfers Ira W. Snyder
2010-09-27 15:23 ` Linus Walleij
2010-09-27 15:23 ` Linus Walleij
2010-09-27 17:23 ` Ira W. Snyder
2010-09-27 17:23 ` Ira W. Snyder
2010-09-27 17:35 ` Dan Williams
2010-09-27 17:35 ` Dan Williams
2010-09-28 7:13 ` Per Förlin [this message]
2010-09-28 7:13 ` Per Förlin
2010-09-24 23:13 ` [PATCH RFCv2 2/2] fsldma: use generic " Ira W. Snyder
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=4CA1959F.8050806@stericsson.com \
--to=per.friden@stericsson.com \
--cc=dan.j.williams@intel.com \
--cc=iws@ovro.caltech.edu \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.