From: Ravi Kumar V <kumarrav@codeaurora.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: linux-arm-kernel@lists.infradead.org, davidb@codeaurora.org,
dan.j.williams@intel.com, Daniel Walker <dwalker@fifo99.com>,
johlstei@codeaurora.org, bryanh@codeaurora.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
arnd@arndb.de, tsoni@codeaurora.org, linux@arm.linux.org.uk
Subject: Re: [PATCH v2 0/2] Add Qualcomm MSM ADM DMAEngine driver
Date: Wed, 01 Feb 2012 14:38:59 +0530 [thread overview]
Message-ID: <4F29012B.50202@codeaurora.org> (raw)
In-Reply-To: <1328086017.1610.13.camel@vkoul-udesk3>
On 2/1/2012 2:16 PM, Vinod Koul wrote:
> On Wed, 2012-02-01 at 14:07 +0530, Ravi Kumar V wrote:
>> Our hardware supports single transfer mode,scatter gather mode& box
>> mode.
>>
>> we are using these dmaengine API's for our HW
>> device_prep_memcpy() for single mode.
>> device_prep_dma_sg() for sg mode.
>> device_prep_interleaved_dma() for box mode.
>>
>> We need to pass command configuration parameter to all of the above
>> three modes and it can be possible if extra context parameter is added
>> into these API's
> but again, is this static fr channel for each transfer. Would you be
> able to derive these for non box modes?
>
Command configuration parameter has this information which is used be our HW
1.Device Id for Synchronization & acknowledgment with slow clock devices.
2.Endian type.
3.Blocking/unblocking channel after/before transfer.
Command configuration parameter should be passed in all the three modes
and per transfer so this parameter is dynamic keep changing for each
transfer.
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: kumarrav@codeaurora.org (Ravi Kumar V)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Add Qualcomm MSM ADM DMAEngine driver
Date: Wed, 01 Feb 2012 14:38:59 +0530 [thread overview]
Message-ID: <4F29012B.50202@codeaurora.org> (raw)
In-Reply-To: <1328086017.1610.13.camel@vkoul-udesk3>
On 2/1/2012 2:16 PM, Vinod Koul wrote:
> On Wed, 2012-02-01 at 14:07 +0530, Ravi Kumar V wrote:
>> Our hardware supports single transfer mode,scatter gather mode& box
>> mode.
>>
>> we are using these dmaengine API's for our HW
>> device_prep_memcpy() for single mode.
>> device_prep_dma_sg() for sg mode.
>> device_prep_interleaved_dma() for box mode.
>>
>> We need to pass command configuration parameter to all of the above
>> three modes and it can be possible if extra context parameter is added
>> into these API's
> but again, is this static fr channel for each transfer. Would you be
> able to derive these for non box modes?
>
Command configuration parameter has this information which is used be our HW
1.Device Id for Synchronization & acknowledgment with slow clock devices.
2.Endian type.
3.Blocking/unblocking channel after/before transfer.
Command configuration parameter should be passed in all the three modes
and per transfer so this parameter is dynamic keep changing for each
transfer.
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-02-01 9:09 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 12:47 [PATCH v2 0/2] Add Qualcomm MSM ADM DMAEngine driver Ravi Kumar V
2012-01-06 12:47 ` Ravi Kumar V
2012-01-06 12:47 ` [PATCH v2 1/2] dmaengine: Add support for per xfer specific privatedata & box dma Ravi Kumar V
2012-01-06 12:47 ` Ravi Kumar V
2012-01-07 0:02 ` David Brown
2012-01-07 0:02 ` David Brown
2012-01-17 13:53 ` Vinod Koul
2012-01-17 13:53 ` Vinod Koul
2012-01-20 12:33 ` Ravi Kumar V
2012-01-20 12:33 ` Ravi Kumar V
2012-01-06 12:47 ` [PATCH v2 2/2] msm: DMAEngine: Add DMAEngine driver based on old MSM DMA APIs Ravi Kumar V
2012-01-06 12:47 ` Ravi Kumar V
2012-01-07 1:59 ` Daniel Walker
2012-01-07 1:59 ` Daniel Walker
2012-01-07 1:59 ` Daniel Walker
2012-01-07 18:54 ` David Brown
2012-01-07 18:54 ` David Brown
2012-01-07 19:21 ` Russell King - ARM Linux
2012-01-07 19:21 ` Russell King - ARM Linux
2012-01-08 0:13 ` Daniel Walker
2012-01-08 0:13 ` Daniel Walker
2012-01-08 0:21 ` Russell King - ARM Linux
2012-01-08 0:21 ` Russell King - ARM Linux
2012-01-09 11:11 ` Ravi Kumar V
2012-01-09 11:11 ` Ravi Kumar V
2012-01-17 6:26 ` Ravi Kumar V
2012-01-17 6:26 ` Ravi Kumar V
2012-01-17 6:32 ` Ravi Kumar V
2012-01-17 6:32 ` Ravi Kumar V
2012-01-17 14:35 ` Vinod Koul
2012-01-17 14:35 ` Vinod Koul
2012-01-20 12:47 ` Ravi Kumar V
2012-01-20 12:47 ` Ravi Kumar V
2012-01-17 14:31 ` Vinod Koul
2012-01-17 14:31 ` Vinod Koul
2012-01-17 14:31 ` Vinod Koul
2012-01-20 12:46 ` Ravi Kumar V
2012-01-20 12:46 ` Ravi Kumar V
2012-01-17 13:45 ` [PATCH v2 0/2] Add Qualcomm MSM ADM DMAEngine driver Vinod Koul
2012-01-17 13:45 ` Vinod Koul
2012-01-20 12:30 ` Ravi Kumar V
2012-01-20 12:30 ` Ravi Kumar V
2012-01-20 13:31 ` Vinod Koul
2012-01-20 13:31 ` Vinod Koul
2012-01-23 11:11 ` Ravi Kumar V
2012-01-23 11:11 ` Ravi Kumar V
2012-01-23 13:51 ` Vinod Koul
2012-01-23 13:51 ` Vinod Koul
2012-01-25 13:11 ` Ravi Kumar V
2012-01-25 13:11 ` Ravi Kumar V
2012-01-30 7:53 ` Ravi Kumar V
2012-01-30 7:53 ` Ravi Kumar V
2012-01-30 8:15 ` Vinod Koul
2012-01-30 8:15 ` Vinod Koul
2012-01-31 5:59 ` Ravi Kumar V
2012-01-31 5:59 ` Ravi Kumar V
2012-01-31 6:09 ` Vinod Koul
2012-01-31 6:09 ` Vinod Koul
2012-02-01 6:16 ` Ravi Kumar V
2012-02-01 6:16 ` Ravi Kumar V
2012-02-01 8:29 ` Vinod Koul
2012-02-01 8:29 ` Vinod Koul
2012-02-01 8:29 ` Vinod Koul
2012-02-01 8:37 ` Ravi Kumar V
2012-02-01 8:46 ` Vinod Koul
2012-02-01 9:08 ` Ravi Kumar V [this message]
2012-02-01 9:08 ` Ravi Kumar V
2012-02-01 8:38 ` Ravi Kumar V
2012-02-01 8:38 ` Ravi Kumar V
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=4F29012B.50202@codeaurora.org \
--to=kumarrav@codeaurora.org \
--cc=arnd@arndb.de \
--cc=bryanh@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=davidb@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=johlstei@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tsoni@codeaurora.org \
--cc=vinod.koul@intel.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.