From: Pratyush Anand <pratyush.anand@st.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
Viresh KUMAR <viresh.kumar@st.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Shiraz HASHIM <shiraz.hashim@st.com>,
Armando VISCONTI <armando.visconti@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>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>
Subject: Re: dmaengine/Query: What about scatter/gather for mem to mem transfers.
Date: Mon, 2 Jan 2012 17:20:49 +0530 [thread overview]
Message-ID: <4F019A19.3060701@st.com> (raw)
In-Reply-To: <1325504133.1540.26.camel@vkoul-udesk3>
On 1/2/2012 5:05 PM, Vinod Koul wrote:
> On Tue, 2011-12-20 at 15:45 +0530, Pratyush Anand wrote:
>> > On 12/20/2011 2:51 PM, Vinod Koul wrote:
>>> > > On Thu, 2011-12-15 at 12:26 +0530, Pratyush Anand wrote:
>>>>>> > >>>> That way existing mechanism would work well for you.
>>>>>> > >>>> You need to split the chunks properly, which is what dma would do
>>>> > >> anyway
>>>>>> > >>>>
>>>>> > >>>
>>>>> > >>> Yes, they can be split like this, but then splitting onus will go on
>>>> > >> dma
>>>>> > >>> user driver, and so there would be replication of similar logic at
>>>>> > >>> several places. Therefore, I was thinking to make device_prep_dma_sg
>>>> > >> as
>>>>> > >>> generic by adding these flags.
>>> > > Well I am not sure how adding flags handles this?
>> >
>> > device_prep_dma_sg has last argument as flags. dma user driver can pass
>> > information about inc/dec of src/dst in this flag, which can be used by
>> > the dma driver. I have put one such implementation at the end of mail.
> with the split pre-done would we need to do this, hence the referred
> implementation.
>
even with pre-done, some flag in this function will be needed. Because
HW also need o know whether to src and dst are in incrementing or
decrementing order.
prev parent reply other threads:[~2012-01-02 11:51 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
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 [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=4F019A19.3060701@st.com \
--to=pratyush.anand@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=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirko.gardi@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 \
--cc=viresh.kumar@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 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).