public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: "Köry Maincent" <kory.maincent@bootlin.com>
Cc: Cai Huoqing <cai.huoqing@linux.dev>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Serge Semin <fancer.lancer@gmail.com>,
	Gustavo Pimentel <Gustavo.Pimentel@synopsys.com>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Herve Codina <herve.codina@bootlin.com>
Subject: Re: [PATCH v2 0/5] Fix support of dw-edma HDMA NATIVE IP in remote setup
Date: Wed, 4 Oct 2023 12:51:54 +0530	[thread overview]
Message-ID: <ZR0SkhEFe7Cc8p3k@matsya> (raw)
In-Reply-To: <20231002131749.2977952-1-kory.maincent@bootlin.com>

On 02-10-23, 15:17, Köry Maincent wrote:
> From: Kory Maincent <kory.maincent@bootlin.com>
> 
> This patch series fix the support of dw-edma HDMA NATIVE IP.
> I can only test it in remote HDMA IP setup with single dma transfer, but
> with these fixes it works properly.
> 
> Few fixes has also been added for eDMA version. Similarly to HDMA I have
> tested only eDMA in remote setup.

Changes in v2...?

> 
> Kory Maincent (5):
>   dmaengine: dw-edma: Fix the ch_count hdma callback
>   dmaengine: dw-edma: Typos fixes
>   dmaengine: dw-edma: Add HDMA remote interrupt configuration
>   dmaengine: dw-edma: HDMA: Add sync read before starting the DMA
>     transfer in remote setup
>   dmaengine: dw-edma: eDMA: Add sync read before starting the DMA
>     transfer in remote setup
> 
>  drivers/dma/dw-edma/dw-edma-v0-core.c | 22 ++++++++++++++
>  drivers/dma/dw-edma/dw-hdma-v0-core.c | 43 +++++++++++++++++++--------
>  drivers/dma/dw-edma/dw-hdma-v0-regs.h |  2 +-
>  3 files changed, 53 insertions(+), 14 deletions(-)
> 
> -- 
> 2.25.1

-- 
~Vinod

  parent reply	other threads:[~2023-10-04  7:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 13:17 [PATCH v2 0/5] Fix support of dw-edma HDMA NATIVE IP in remote setup Köry Maincent
2023-10-02 13:17 ` [PATCH v2 1/5] dmaengine: dw-edma: Fix the ch_count hdma callback Köry Maincent
2023-10-03 11:23   ` Serge Semin
2023-10-10 14:56   ` Manivannan Sadhasivam
2023-10-02 13:17 ` [PATCH v2 2/5] dmaengine: dw-edma: Typos fixes Köry Maincent
2023-10-10 14:59   ` Manivannan Sadhasivam
2023-10-11  7:23     ` Köry Maincent
2023-10-11 10:38       ` Serge Semin
2023-10-02 13:17 ` [PATCH v2 3/5] dmaengine: dw-edma: Add HDMA remote interrupt configuration Köry Maincent
2023-10-10 15:00   ` Manivannan Sadhasivam
2023-10-02 13:17 ` [PATCH v2 4/5] dmaengine: dw-edma: HDMA: Add sync read before starting the DMA transfer in remote setup Köry Maincent
2023-10-03 11:48   ` Serge Semin
2023-10-03 12:15     ` Köry Maincent
2023-10-03 15:20       ` Serge Semin
2023-10-03 15:34         ` Köry Maincent
2023-10-03 15:57           ` Serge Semin
2023-10-02 13:17 ` [PATCH v2 5/5] dmaengine: dw-edma: eDMA: " Köry Maincent
2023-10-03 11:59   ` Serge Semin
2023-10-03 12:17     ` Köry Maincent
2023-10-04  7:21 ` Vinod Koul [this message]
2023-10-04  8:04   ` [PATCH v2 0/5] Fix support of dw-edma HDMA NATIVE IP " Köry Maincent

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=ZR0SkhEFe7Cc8p3k@matsya \
    --to=vkoul@kernel.org \
    --cc=Gustavo.Pimentel@synopsys.com \
    --cc=cai.huoqing@linux.dev \
    --cc=dmaengine@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=herve.codina@bootlin.com \
    --cc=kory.maincent@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=thomas.petazzoni@bootlin.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