[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191105151353.6522-1-andrew.smirnov@gmail.com>
Date: Tue, 5 Nov 2019 07:13:48 -0800
From: Andrey Smirnov <andrew.smirnov@...il.com>
To: linux-crypto@...r.kernel.org
Cc: Andrey Smirnov <andrew.smirnov@...il.com>,
Chris Healy <cphealy@...il.com>,
Lucas Stach <l.stach@...gutronix.de>,
Horia Geantă <horia.geanta@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Iuliana Prodan <iuliana.prodan@....com>, linux-imx@....com,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] CAAM JR lifecycle
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@...il.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
Powered by blists - more mailing lists