On Sat, Jun 20, 2015 at 4:32 PM, Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx> wrote: > On Fri, Jun 19, 2015 at 10:24 AM, Herbert Xu > <herbert@xxxxxxxxxxxxxxxxxxx> wrote: >> On Thu, Jun 18, 2015 at 03:46:16PM +0200, Boris Brezillon wrote: >>> Hello, >>> >>> This patch series adds a new driver supporting Marvell's CESA IP. >>> This driver addresses some limitations of the existing one. >>> >From a performance and CPU load point of view the most important >>> limitation in the existing driver is the lack of DMA support, thus >>> preventing us from chaining crypto operations. >> >> All applied to cryptodev. Thanks a lot! > > It seems this breaks linux-next allmodconfig on i386: Similar breakage for s390 and sparc it seems: drivers/crypto/marvell/cesa.c:353:2: error: implicit declaration of function 'phys_to_dma' [-Werror=implicit-function-declaration] http://kisskb.ellerman.id.au/kisskb/buildresult/12445415/ http://kisskb.ellerman.id.au/kisskb/buildresult/12445345/ If the CESA IP is only available on a single arch then adding an arch dependency might be the easiest fix, since phys_to_dma seems sparsely implemented. Paul. -- > > http://kisskb.ellerman.id.au/kisskb/buildresult/12445342/ > > ERROR: "phys_to_dma" [drivers/crypto/marvell/marvell-cesa.ko] undefined! > make[2]: *** [__modpost] Error 1 > > Paul. > -- -- To unsubscribe from this list: send the line "unsubscribe devicetree" in
