From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] dmaengine: xilinx_vdma: Improve SG engine handling
Date: Thu, 3 Mar 2016 21:03:23 +0530 [thread overview]
Message-ID: <20160303153323.GN11154@localhost> (raw)
In-Reply-To: <1456495434-11722-1-git-send-email-appanad@xilinx.com>
On Fri, Feb 26, 2016 at 07:33:51PM +0530, Kedareswara rao Appana wrote:
> The current driver allows user to queue up multiple segments
> on to a single transaction descriptor. User will submit this single desc
> and in the issue_pending() we decode multiple segments and submit to SG HW engine.
> We free up the allocated_desc when it is submitted to the HW.
>
> Existing code prevents the user to prepare multiple trasactions at same time as
> we are overwrite with the allocated_desc.
>
> The best utilization of HW SG engine would happen if we collate the pending
> list when we start dma this patch updates the same.
Applied all. It is usually advisable to do cover letter using --cover-letter
for multi patch series
--
~Vinod
next prev parent reply other threads:[~2016-03-03 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 14:03 [PATCH v3 1/4] dmaengine: xilinx_vdma: Improve SG engine handling Kedareswara rao Appana
2016-02-26 14:03 ` [PATCH v3 2/4] dmaengine: xilinx_vdma: Simplify spin lock handling Kedareswara rao Appana
2016-02-26 14:03 ` [PATCH v3 3/4] dmaengine: xilinx_vdma: Fix issues with non-parking mode Kedareswara rao Appana
2016-02-26 14:03 ` [PATCH v3 4/4] dmaengine: xilinx_vdma: Use readl_poll_timeout instead of do while loop's Kedareswara rao Appana
2016-03-03 15:29 ` Vinod Koul
2016-03-03 17:12 ` Appana Durga Kedareswara Rao
2016-03-03 15:33 ` Vinod Koul [this message]
2016-03-03 16:28 ` [PATCH v3 1/4] dmaengine: xilinx_vdma: Improve SG engine handling Appana Durga Kedareswara Rao
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=20160303153323.GN11154@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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 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).