From: Viresh Kumar <viresh.kumar@st.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Armando VISCONTI <armando.visconti@st.com>,
Pratyush ANAND <pratyush.anand@st.com>,
Deepak SIKRI <deepak.sikri@st.com>,
Vipin KUMAR <vipin.kumar@st.com>,
Vipul Kumar SAMAR <vipulkumar.samar@st.com>,
Vincenzo FRASCINO <Vincenzo.FRASCINO@st.com>,
Mirko GARDI <mirko.gardi@st.com>,
Rajeev KUMAR <rajeev-dlh.kumar@st.com>,
Amit VIRDI <Amit.VIRDI@st.com>,
Bhupesh SHARMA <bhupesh.sharma@st.com>
Subject: Re: dmaengine/Query: What about scatter/gather for mem to mem transfers.
Date: Thu, 8 Dec 2011 13:20:20 +0530 [thread overview]
Message-ID: <4EE06C3C.8080003@st.com> (raw)
In-Reply-To: <1323329870.1641.27.camel@vkoul-udesk3>
On 12/8/2011 1:07 PM, Vinod Koul wrote:
> You mean something like:
> struct dma_async_tx_descriptor *(*device_prep_dma_sg)(
> struct dma_chan *chan,
> struct scatterlist *dst_sg, unsigned int dst_nents,
> struct scatterlist *src_sg, unsigned int src_nents,
> unsigned long flags);
>
> Its already there, you need to implement in your driver :)
Ok. I didn't knew it. :(
--
viresh
next prev parent reply other threads:[~2011-12-08 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 4:10 dmaengine/Query: What about scatter/gather for mem to mem transfers Viresh Kumar
2011-12-08 7:37 ` Vinod Koul
2011-12-08 7:50 ` Viresh Kumar [this message]
2011-12-14 6:47 ` Pratyush Anand
2011-12-15 4:58 ` Pratyush Anand
2011-12-15 5:06 ` Koul, Vinod
2011-12-15 5:24 ` Pratyush Anand
2011-12-15 6:56 ` Pratyush Anand
2011-12-20 9:21 ` Vinod Koul
2011-12-20 10:15 ` Pratyush Anand
2012-01-02 11:35 ` Vinod Koul
2012-01-02 11:50 ` Pratyush Anand
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=4EE06C3C.8080003@st.com \
--to=viresh.kumar@st.com \
--cc=Amit.VIRDI@st.com \
--cc=Vincenzo.FRASCINO@st.com \
--cc=armando.visconti@st.com \
--cc=bhupesh.sharma@st.com \
--cc=dan.j.williams@intel.com \
--cc=deepak.sikri@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mirko.gardi@st.com \
--cc=pratyush.anand@st.com \
--cc=rajeev-dlh.kumar@st.com \
--cc=shiraz.hashim@st.com \
--cc=vinod.koul@intel.com \
--cc=vipin.kumar@st.com \
--cc=vipulkumar.samar@st.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.