All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: dmaengine@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	geert+renesas@glider.be,
	laurent.pinchart+renesas@ideasonboard.com, mfarooq@visteon.com
Subject: Re: [PATCHv2 0/4] Residue patches for rcar-dmac from renesas-drivers
Date: Fri, 8 Jul 2016 11:09:38 +0530	[thread overview]
Message-ID: <20160708053937.GO12591@localhost> (raw)
In-Reply-To: <20160630151518.32329-1-niklas.soderlund+renesas@ragnatech.se>

On Thu, Jun 30, 2016 at 05:15:14PM +0200, Niklas S�derlund wrote:
> Hi all,
> 
> I have looked over the DMA residue branches in renesas-drivers tree
> (topic/rcar-dmac-hamza-v3 and topic/rcar-dmac-residue-v1) hoping to
> bring them to upstream. The original author for the bulk of the patches
> Hamza Farooq have not shown any activity since autumn 2015.
> 
> In this cover letter I talk about all the patches in the above branches
> but for obvious reasons only patches I think should be forwarded to
> upstream are included in the series. All patches are based on top of
> v4.7-rc1 and are tested on Koelsch using Geerts sertest tool to generate
> DMA traffic. The highest baud I could get to work at was 921600 bps.
> From reading the original mail threads my conclusion is that this is
> good enough since all errors reported by Hamza Farooq where related to
> the serial sh-sci driver.

Applied all, thanks

-- 
~Vinod

  parent reply	other threads:[~2016-07-08  5:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 15:15 [PATCHv2 0/4] Residue patches for rcar-dmac from renesas-drivers Niklas Söderlund
2016-06-30 15:15 ` [PATCHv2 1/4] dmaengine: rcar-dmac: use result of updated get_residue in tx_status Niklas Söderlund
2016-06-30 15:15 ` [PATCHv2 2/4] dmaengine: rcar-dmac: warn if transfer cannot start as TE = 1 Niklas Söderlund
2016-06-30 15:15 ` [PATCHv2 3/4] dmaengine: rcar-dmac: Fixed active descriptor initializing Niklas Söderlund
2016-06-30 15:15 ` [PATCHv2 4/4] dmaengine: rcar-dmac: Fix residue reporting for pending descriptors Niklas Söderlund
2016-07-08  5:39 ` Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-15 12:44 [PATCHv2,1/4] dmaengine: rcar-dmac: use result of updated get_residue in tx_status Dirk Behme
2019-01-15 12:44 ` [PATCHv2 1/4] " Dirk Behme
2019-01-21  3:16 [PATCHv2,1/4] " Yoshihiro Shimoda
2019-01-21  3:16 ` [PATCHv2 1/4] " Yoshihiro Shimoda

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=20160708053937.GO12591@localhost \
    --to=vinod.koul@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mfarooq@visteon.com \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    /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.