dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, Michal Simek <michal.simek@xilinx.com>,
	Hyun Kwon <hyun.kwon@xilinx.com>,
	Tejas Upadhyay <tejasu@xilinx.com>,
	Satish Kumar Nagireddy <SATISHNA@xilinx.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH v7 0/5] dma: Add Xilinx ZynqMP DPDMA driver
Date: Sat, 18 Jul 2020 03:24:16 +0300	[thread overview]
Message-ID: <20200718002416.GC5962@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200717061120.GE82923@vkoul-mobl>

Hi Vinod,

On Fri, Jul 17, 2020 at 11:41:20AM +0530, Vinod Koul wrote:
> On 17-07-20, 04:33, Laurent Pinchart wrote:
> > Hello,
> > 
> > This patch series adds a new driver for the DPDMA engine found in the
> > Xilinx ZynqMP.
> > 
> > The previous version can be found at [1]. All review comments have been
> > taken into account. The main changes are in the DPDMA driver, with
> > cleanups in the debugfs support, and handling of the !LOAD_EOT case when
> > preparing transactions.
> > 
> > The driver has been successfully tested with the ZynqMP DisplayPort
> > subsystem DRM driver.
> > 
> > As I would like to merge both this series and the DRM driver that
> > depends on it for v5.9 (if still possible), I have based those patches
> > on top of v5.8-rc1. There's unfortunately a conflict with the DMA engine
> > next branch, which is easy to resolve.
> > 
> > Vinod, if you're fine with the series, I can propose two ways forward:
> > 
> > - You can apply the patches on top of v5.8-rc1, push that to a base
> >   branch, merge it into the dmaengine -next branch, and push the base
> >   branch to a public git tree to let me base the DRM driver on it.
> 
> Applied 1-3 to dmaengine.git topic/xilinx, it should show up in -next
> later in the day

Thank you!

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2020-07-18  0:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  1:33 [PATCH v7 0/5] dma: Add Xilinx ZynqMP DPDMA driver Laurent Pinchart
2020-07-17  1:33 ` [PATCH v7 1/5] dt: bindings: dma: xilinx: dpdma: DT bindings for Xilinx DPDMA Laurent Pinchart
2020-07-17  1:33 ` [PATCH v7 2/5] dmaengine: Add support for repeating transactions Laurent Pinchart
2020-07-17  1:33 ` [PATCH v7 3/5] dmaengine: xilinx: dpdma: Add the Xilinx DisplayPort DMA engine driver Laurent Pinchart
2020-07-17  1:33 ` [PATCH v7 4/5] dmaengine: xilinx: dpdma: Add debugfs support Laurent Pinchart
2020-07-17  6:05   ` Vinod Koul
2020-07-18  0:23     ` Laurent Pinchart
2020-07-17  1:33 ` [PATCH v7 5/5] arm64: dts: zynqmp: Add DPDMA node Laurent Pinchart
2020-07-17  6:11 ` [PATCH v7 0/5] dma: Add Xilinx ZynqMP DPDMA driver Vinod Koul
2020-07-18  0:24   ` Laurent Pinchart [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=20200718002416.GC5962@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=SATISHNA@xilinx.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=hyun.kwon@xilinx.com \
    --cc=michal.simek@xilinx.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=tejasu@xilinx.com \
    --cc=vkoul@kernel.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).