linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: mv_xor_v2: new driver
Date: Fri, 17 Jun 2016 08:09:20 +0530	[thread overview]
Message-ID: <20160617023920.GE16910@localhost> (raw)
In-Reply-To: <20160616144224.2e687a14@free-electrons.com>

On Thu, Jun 16, 2016 at 02:42:24PM +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 15 Jun 2016 22:11:31 +0530, Vinod Koul wrote:
> 
> > > This is probably the only thing that I have not changed. The mv_xor
> > > driver is already using the same strategy, and enqueuing in
> > > issue_pending() would force us to add the request to a temporary linked
> > > list, which would be dequeued in issue_pending(). This is quite a bit
> > > of additional processing, while pushing the new requests directly to
> > > the engine works fine.  
> > 
> > Well that is wrong! And patch is welcome for mv_xor as well :)
> > 
> > The DMAengine API mandates that we should submit a descriptor to a queue and
> > then push them by invoking issue_pending.
> > 
> > The users are also expected to follow this
> 
> I have just sent a v4 that fixes this for the mv_xor_v2 driver. Now, in
> ->tx_submit() we only fill in the HW descriptors, but do not tell the
> engine to process them. It's only at ->issue_pending() time that we
> tell the engine that there N new descriptors to process.

Okay that sounds good to me, I will take a look at it..
> 
> I'll have a look at mv_xor a bit later.

Sounds fair enough

-- 
~Vinod

      reply	other threads:[~2016-06-17  2:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15  7:58 [PATCH] dma: mv_xor_v2: new driver Thomas Petazzoni
2016-02-15  9:09 ` kbuild test robot
2016-02-15  9:50   ` Thomas Petazzoni
2016-02-15  9:59     ` Marc Zyngier
2016-02-15 10:58       ` Thomas Petazzoni
2016-02-15  9:34 ` [PATCH] dma: mv_xor_v2: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-02-15  9:34 ` [PATCH] dma: mv_xor_v2: new driver kbuild test robot
2016-02-15  9:56 ` kbuild test robot
2016-02-22  2:53 ` Rob Herring
2016-02-22  7:21   ` Thomas Petazzoni
2016-02-22 20:02     ` Rob Herring
2016-02-22  3:27 ` Vinod Koul
2016-02-22  9:16   ` Thomas Petazzoni
2016-02-22 19:58     ` Rob Herring
2016-02-23  3:02     ` Vinod Koul
2016-06-15 14:08   ` Thomas Petazzoni
2016-06-15 16:41     ` Vinod Koul
2016-06-16 12:42       ` Thomas Petazzoni
2016-06-17  2:39         ` Vinod Koul [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=20160617023920.GE16910@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).