From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: mv_xor_v2: new driver
Date: Wed, 15 Jun 2016 22:11:31 +0530 [thread overview]
Message-ID: <20160615164131.GB16910@localhost> (raw)
In-Reply-To: <20160615160837.64377829@free-electrons.com>
On Wed, Jun 15, 2016 at 04:08:37PM +0200, Thomas Petazzoni wrote:
> > > + (xor_dev->desc_size * desq_ptr));
> > > +
> > > + memcpy(dest_hw_desc, &sw_desc->hw_desc, xor_dev->desc_size);
> > > +
> > > + /* update the DMA Engine with the new descriptor */
> > > + mv_xor_v2_add_desc_to_desq(xor_dev, 1);
> > > +
> > > + /* unlock enqueue DESCQ */
> > > + spin_unlock_bh(&xor_dev->push_lock);
> >
> > and if IIUC, you are pushing this to HW as well, that is not quite right if
> > thats the case. We need to do this in issue_pending
>
> 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
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Thomas Petazzoni
<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Gregory Clement
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Nadav Haklai <nadavh-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
Lior Amsalem <alior-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] dma: mv_xor_v2: new driver
Date: Wed, 15 Jun 2016 22:11:31 +0530 [thread overview]
Message-ID: <20160615164131.GB16910@localhost> (raw)
In-Reply-To: <20160615160837.64377829-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
On Wed, Jun 15, 2016 at 04:08:37PM +0200, Thomas Petazzoni wrote:
> > > + (xor_dev->desc_size * desq_ptr));
> > > +
> > > + memcpy(dest_hw_desc, &sw_desc->hw_desc, xor_dev->desc_size);
> > > +
> > > + /* update the DMA Engine with the new descriptor */
> > > + mv_xor_v2_add_desc_to_desq(xor_dev, 1);
> > > +
> > > + /* unlock enqueue DESCQ */
> > > + spin_unlock_bh(&xor_dev->push_lock);
> >
> > and if IIUC, you are pushing this to HW as well, that is not quite right if
> > thats the case. We need to do this in issue_pending
>
> 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
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-15 16:41 UTC|newest]
Thread overview: 38+ 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 7:58 ` Thomas Petazzoni
2016-02-15 9:09 ` kbuild test robot
2016-02-15 9:09 ` kbuild test robot
2016-02-15 9:50 ` Thomas Petazzoni
2016-02-15 9:50 ` Thomas Petazzoni
2016-02-15 9:59 ` Marc Zyngier
2016-02-15 9:59 ` Marc Zyngier
2016-02-15 10:58 ` Thomas Petazzoni
2016-02-15 10:58 ` Thomas Petazzoni
2016-02-15 9:34 ` kbuild test robot
2016-02-15 9:34 ` kbuild test robot
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 ` kbuild test robot
2016-02-15 9:56 ` [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 2:53 ` Rob Herring
2016-02-22 7:21 ` Thomas Petazzoni
2016-02-22 7:21 ` Thomas Petazzoni
2016-02-22 20:02 ` Rob Herring
2016-02-22 20:02 ` Rob Herring
2016-02-22 3:27 ` Vinod Koul
2016-02-22 3:27 ` Vinod Koul
2016-02-22 9:16 ` Thomas Petazzoni
2016-02-22 9:16 ` Thomas Petazzoni
2016-02-22 19:58 ` Rob Herring
2016-02-22 19:58 ` Rob Herring
2016-02-23 3:02 ` Vinod Koul
2016-02-23 3:02 ` Vinod Koul
2016-06-15 14:08 ` Thomas Petazzoni
2016-06-15 14:08 ` Thomas Petazzoni
2016-06-15 16:41 ` Vinod Koul [this message]
2016-06-15 16:41 ` Vinod Koul
2016-06-16 12:42 ` Thomas Petazzoni
2016-06-16 12:42 ` Thomas Petazzoni
2016-06-17 2:39 ` Vinod Koul
2016-06-17 2:39 ` Vinod Koul
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=20160615164131.GB16910@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 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.