From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: "Andrey Smirnov" <andrew.smirnov@gmail.com>,
"Chris Healy" <cphealy@gmail.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Iuliana Prodan" <iuliana.prodan@nxp.com>,
linux-imx@nxp.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] CAAM JR lifecycle
Date: Tue, 5 Nov 2019 07:13:48 -0800 [thread overview]
Message-ID: <20191105151353.6522-1-andrew.smirnov@gmail.com> (raw)
Everyone:
This series is a different approach to addressing the issues brought
up in [discussion]. This time the proposition is to get away from
creating per-JR platfrom device, move all of the underlying code into
caam.ko and disable manual binding/unbinding of the CAAM device via
sysfs. Note that this series is a rough cut intented to gauge if this
approach could be acceptable for upstreaming.
Thanks,
Andrey Smirnov
[discussion] lore.kernel.org/lkml/20190904023515.7107-13-andrew.smirnov@gmail.com
Andrey Smirnov (5):
crypto: caam - use static initialization
crypto: caam - introduce caam_jr_cbk
crypto: caam - convert JR API to use struct caam_drv_private_jr
crypto: caam - do not create a platform devices for JRs
crypto: caam - disable CAAM's bind/unbind attributes
drivers/crypto/caam/Kconfig | 5 +-
drivers/crypto/caam/Makefile | 15 +--
drivers/crypto/caam/caamalg.c | 114 ++++++++++----------
drivers/crypto/caam/caamalg_qi.c | 12 +--
drivers/crypto/caam/caamhash.c | 117 +++++++++++----------
drivers/crypto/caam/caampkc.c | 67 ++++++------
drivers/crypto/caam/caampkc.h | 2 +-
drivers/crypto/caam/caamrng.c | 41 ++++----
drivers/crypto/caam/ctrl.c | 16 ++-
drivers/crypto/caam/intern.h | 3 +-
drivers/crypto/caam/jr.c | 173 ++++++++-----------------------
drivers/crypto/caam/jr.h | 14 ++-
drivers/crypto/caam/key_gen.c | 11 +-
drivers/crypto/caam/key_gen.h | 5 +-
14 files changed, 275 insertions(+), 320 deletions(-)
--
2.21.0
next reply other threads:[~2019-11-05 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 15:13 Andrey Smirnov [this message]
2019-11-05 15:13 ` [PATCH 1/5] crypto: caam - use static initialization Andrey Smirnov
2019-11-20 7:06 ` Horia Geanta
2019-11-05 15:13 ` [PATCH 2/5] crypto: caam - introduce caam_jr_cbk Andrey Smirnov
2019-11-20 7:09 ` Horia Geanta
2019-11-05 15:13 ` [PATCH 3/5] crypto: caam - convert JR API to use struct caam_drv_private_jr Andrey Smirnov
2019-11-06 9:04 ` kbuild test robot
2019-11-05 15:13 ` [PATCH 4/5] crypto: caam - do not create a platform devices for JRs Andrey Smirnov
2019-11-05 15:13 ` [PATCH 5/5] crypto: caam - disable CAAM's bind/unbind attributes Andrey Smirnov
2019-11-06 7:27 ` [PATCH 0/5] CAAM JR lifecycle Vakul Garg
2019-11-06 15:19 ` Andrey Smirnov
2019-11-13 18:57 ` Horia Geanta
2019-11-13 19:25 ` Andrey Smirnov
2019-11-17 6:15 ` Andrey Smirnov
2020-01-08 15:50 ` Andrey Smirnov
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=20191105151353.6522-1-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=iuliana.prodan@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®