From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux@arm.linux.org.uk, tony@atomide.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
dan.j.williams@intel.com
Subject: Re: [PATCH] dmaengine: omap-dma: Add support for memcpy
Date: Mon, 4 May 2015 14:05:45 +0530 [thread overview]
Message-ID: <20150504083545.GD3521@localhost> (raw)
In-Reply-To: <1429688069-31765-1-git-send-email-peter.ujfalusi@ti.com>
On Wed, Apr 22, 2015 at 10:34:29AM +0300, Peter Ujfalusi wrote:
> The sDMA controller is capable of performing memory copy operation. It need
> to be configured to software triggered mode and without HW synchronization.
> The sDMA can copy data which is aligned to 8, 16 or 32 bits.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: omap-dma: Add support for memcpy
Date: Mon, 4 May 2015 14:05:45 +0530 [thread overview]
Message-ID: <20150504083545.GD3521@localhost> (raw)
In-Reply-To: <1429688069-31765-1-git-send-email-peter.ujfalusi@ti.com>
On Wed, Apr 22, 2015 at 10:34:29AM +0300, Peter Ujfalusi wrote:
> The sDMA controller is capable of performing memory copy operation. It need
> to be configured to software triggered mode and without HW synchronization.
> The sDMA can copy data which is aligned to 8, 16 or 32 bits.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2015-05-04 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 7:34 [PATCH] dmaengine: omap-dma: Add support for memcpy Peter Ujfalusi
2015-04-22 7:34 ` Peter Ujfalusi
2015-04-22 7:34 ` Peter Ujfalusi
2015-05-04 8:35 ` Vinod Koul [this message]
2015-05-04 8:35 ` Vinod Koul
2015-09-08 11:24 ` Laurent Pinchart
2015-09-08 11:24 ` Laurent Pinchart
2015-09-08 12:25 ` Peter Ujfalusi
2015-09-08 12:25 ` Peter Ujfalusi
2015-09-08 12:25 ` Peter Ujfalusi
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=20150504083545.GD3521@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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.