From: =?iso-8859-2?Q?Horia_Geant=E3?= Subject: Re: [PATCH RESEND 1/4] crypto: caam: add caam-dma node to SEC4.0 device tree binding Date: Mon, 13 Nov 2017 08:32:24 +0000 Message-ID: References: <20171030134654.13729-1-horia.geanta@nxp.com> <20171030134654.13729-2-horia.geanta@nxp.com> <20171030092424.1279add003c96ced4233bd2d@arm.com> <20171109103437.834f8ddb5c62e5253002b2d0@arm.com> <20171110104430.28b2f56f910b7514d778c4b2@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Cc: Vinod Koul , Herbert Xu , "David S. Miller" , "Dan Douglass" , Shawn Guo , "dmaengine@vger.kernel.org" , "linux-crypto@vger.kernel.org" , "devicetree@vger.kernel.org" To: Kim Phillips , Radu Andrei Alexe Return-path: Received: from mail-eopbgr00072.outbound.protection.outlook.com ([40.107.0.72]:10684 "EHLO EUR02-AM5-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751905AbdKMIc3 (ORCPT ); Mon, 13 Nov 2017 03:32:29 -0500 Content-Language: en-US Sender: linux-crypto-owner@vger.kernel.org List-ID: On 11/10/2017 6:44 PM, Kim Phillips wrote:=0A= > On Fri, 10 Nov 2017 08:02:01 +0000=0A= > Radu Andrei Alexe wrote:=0A= [snip]>> 2. I wanted this driver to be tracked by the dma engine team.=0A= They have=0A= >> the right expertise to provide adequate feedback. If all the code was in= =0A= >> the crypto directory they wouldn't know about this driver or any =0A= >> subsequent changes to it.=0A= > =0A= > dma subsystem bits could still be put in the dma area if deemed=0A= > necessary but I don't think it is: I see=0A= > drivers/crypto/ccp/ccp-dmaengine.c calls dma_async_device_register for=0A= > example.=0A= > =0A= Please see previous discussion with Vinod:=0A= https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg21468.html=0A= =0A= > What is the rationale for using the crypto h/w as a dma engine anyway?=0A= SoCs that don't have a system DMA, for e.g. LS1012A.=0A= =0A= Horia=0A=