2017-10-27 11:00:18

by Horia Geantă

[permalink] [raw]
Subject: Re: [PATCH 0/4] add CAAM DMA memcpy driver

On 10/26/2017 1:01 PM, Radu Alexe wrote:
> This patch-set introduces a new DMA memcpy driver based on the DMA
> capabilities of the CAAM crypto engine. Because of this dependency the
> included commits target various parts of the kernel tree.
I don't see the patches on any of the mail lists.
If they are moderated, I would expect this to be mentioned in the
MAINTAINERS file.

>
> Patch 1.
> Since the CAAM DMA driver is a platform driver it is enabled by a new node
> in the device tree. This commit adds documentation for the device tree
> bindings.
>
> Patch 2.
> This patch adds the "caam-dma" node in the fsl-ls1012a.dtsi file.
>
> Patch 3.
> This commit adds various capabilities in the JR driver of the CAAM that is
> used by the CAAM DMA driver.
>
> Patch 4.
> Adds the CAAM DMA memcpy driver.
>
> Patch 1 and 3 should be merged by the crypto maintainers, patch 2 by
> devicetree maintainers and patch 4 by the DMA maintainers.
I would go with all the patches through the dmaengine tree.

Horia


2017-10-27 11:36:03

by Vinod Koul

[permalink] [raw]
Subject: RE: [PATCH 0/4] add CAAM DMA memcpy driver

> On 10/26/2017 1:01 PM, Radu Alexe wrote:
> > This patch-set introduces a new DMA memcpy driver based on the DMA
> > capabilities of the CAAM crypto engine. Because of this dependency the
> > included commits target various parts of the kernel tree.
> I don't see the patches on any of the mail lists.
> If they are moderated, I would expect this to be mentioned in the
> MAINTAINERS file.
>
> >
> > Patch 1.
> > Since the CAAM DMA driver is a platform driver it is enabled by a new node
> > in the device tree. This commit adds documentation for the device tree
> > bindings.
> >
> > Patch 2.
> > This patch adds the "caam-dma" node in the fsl-ls1012a.dtsi file.
> >
> > Patch 3.
> > This commit adds various capabilities in the JR driver of the CAAM that is
> > used by the CAAM DMA driver.
> >
> > Patch 4.
> > Adds the CAAM DMA memcpy driver.
> >
> > Patch 1 and 3 should be merged by the crypto maintainers, patch 2 by
> > devicetree maintainers and patch 4 by the DMA maintainers.
> I would go with all the patches through the dmaengine tree.

Good call, but no one CCed dmaengine folks on this series!

--
~Vinod