From: Joel Fernandes <joelf@ti.com>
To: Thomas Gleixner <tglx@linutronix.de>, dmaengine@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, dan.j.williams@intel.com,
vinod.koul@intel.com, nsekhar@ti.com,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [patch V2 0/6] dma: edma: Provide granular residue accounting
Date: Mon, 28 Apr 2014 15:47:37 -0500 [thread overview]
Message-ID: <535EBE69.6060803@ti.com> (raw)
In-Reply-To: <20140428104416.464002156@linutronix.de>
On 04/28/2014 05:49 AM, Thomas Gleixner wrote:
> A simpler version to provide granular residue accounting and readout
> for EDMA.
>
> Delta to V1:
>
> - Removed the double read of the address in PaRAM
>
> - Simplified the stats update in the interrupt callback for
> intermediate transfers
>
> Thanks,
>
> tglx
>
Thanks for the series. I went over all the patches and it looks great.
Acked-by: Joel Fernandes <joelf@ti.com>
The patches however didn't apply and had some conflicts with my dma
memcpy series and peter's cyclic series so I resolved conflicts and
created a single branch based on Vinod's slave-dma next branch (commit
406efb1a745c1dc512dc9c3c859e302e7b7f907e) that Vinod can pull.
I also renamed subject line of patches in Thomas's series to be
"dmaengine: edma" and documented some of the variables used.
https://github.com/joelagnel/linux-kernel.git (for-vinod branch)
Vinod, could you pull if it looks OK?
regards,
-Joel
next parent reply other threads:[~2014-04-28 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140428104416.464002156@linutronix.de>
2014-04-28 20:47 ` Joel Fernandes [this message]
2014-04-29 8:46 ` [patch V2 0/6] dma: edma: Provide granular residue accounting Vinod Koul
2014-04-30 4:25 ` Joel Fernandes
2014-04-30 5:08 ` Vinod Koul
2014-05-01 1:57 ` Joel Fernandes
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=535EBE69.6060803@ti.com \
--to=joelf@ti.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox