From: Michael Ellerman Subject: Re: [7/7] crypto: caam/qi - add ablkcipher and authenc algorithms Date: Wed, 05 Apr 2017 20:06:50 +1000 Message-ID: <87lgrftbgl.fsf@concordia.ellerman.id.au> References: <20170317100602.2837-8-horia.geanta@nxp.com> <87vaqkvk6c.fsf@concordia.ellerman.id.au> <58E39F90.6050408@nxp.com> Mime-Version: 1.0 Content-Type: text/plain Cc: Claudiu Manoil , Cristian Stoica , Dan Douglass , "linux-arm-kernel\@lists.infradead.org" , Vakul Garg , "linuxppc-dev\@lists.ozlabs.org" , "David S. Miller" , Alexandru Porosanu , "linux-crypto\@vger.kernel.org" To: Laurentiu Tudor , Horia =?utf-8?Q?Geant=C4=83?= , Herbert Xu , Scott Wood , Roy Pledge Return-path: Received: from ozlabs.org ([103.22.144.67]:47019 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755214AbdDEKHC (ORCPT ); Wed, 5 Apr 2017 06:07:02 -0400 In-Reply-To: <58E39F90.6050408@nxp.com> Sender: linux-crypto-owner@vger.kernel.org List-ID: Laurentiu Tudor writes: > Hi Michael, > > Just a couple of basic things to check: > - was the dtb updated to the newest? Possibly not, it's an automated build/boot, I'll have to check what it does with the dtb. > - is the qman node present? This should be easily visible in > /proc/device-tree/soc@ffe000000/qman@318000. No it's not there. That's running linux-next with: CONFIG_CRYPTO_DEV_FSL_CAAM_CRYPTO_API_QI=n Does that mean I didn't update the device tree? cheers