From: Michael Ellerman <mpe@ellerman•id.au>
To: "Laurentiu Tudor" <laurentiu.tudor@nxp•com>,
"Horia Geantă" <horia.geanta@nxp•com>,
"Herbert Xu" <herbert@gondor•apana.org.au>,
"Scott Wood" <oss@buserror•net>,
"Roy Pledge" <roy.pledge@nxp•com>
Cc: Claudiu Manoil <claudiu.manoil@nxp•com>,
Cristian Stoica <cristian.stoica@nxp•com>,
Dan Douglass <dan.douglass@nxp•com>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists•infradead.org>,
Vakul Garg <vakul.garg@nxp•com>,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
"David S. Miller" <davem@davemloft•net>,
Alexandru Porosanu <alexandru.porosanu@nxp•com>,
"linux-crypto\@vger.kernel.org" <linux-crypto@vger•kernel.org>
Subject: Re: [7/7] crypto: caam/qi - add ablkcipher and authenc algorithms
Date: Wed, 05 Apr 2017 20:06:50 +1000 [thread overview]
Message-ID: <87lgrftbgl.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <58E39F90.6050408@nxp.com>
Laurentiu Tudor <laurentiu.tudor@nxp•com> 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
next prev parent reply other threads:[~2017-04-05 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170317100602.2837-8-horia.geanta@nxp.com>
2017-04-04 5:03 ` [7/7] crypto: caam/qi - add ablkcipher and authenc algorithms Michael Ellerman
2017-04-04 13:28 ` Laurentiu Tudor
2017-04-05 10:06 ` Michael Ellerman [this message]
2017-04-05 11:49 ` Laurentiu Tudor
2017-04-07 13:21 ` Michael Ellerman
2017-04-07 14:00 ` Laurentiu Tudor
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=87lgrftbgl.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=alexandru.porosanu@nxp$(echo .)com \
--cc=claudiu.manoil@nxp$(echo .)com \
--cc=cristian.stoica@nxp$(echo .)com \
--cc=dan.douglass@nxp$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=horia.geanta@nxp$(echo .)com \
--cc=laurentiu.tudor@nxp$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=oss@buserror$(echo .)net \
--cc=roy.pledge@nxp$(echo .)com \
--cc=vakul.garg@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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