From: Corentin Labbe <clabbe@baylibre.com>
To: heiko@sntech.de, davem@davemloft.net,
herbert@gondor.apana.org.au, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Corentin Labbe <clabbe@baylibre.com>
Subject: [PATCH RFT 1/5] crypto: rockchip: move kconfig to its dedicated directory
Date: Tue, 27 Sep 2022 08:00:44 +0000 [thread overview]
Message-ID: <20220927080048.3151911-2-clabbe@baylibre.com> (raw)
In-Reply-To: <20220927080048.3151911-1-clabbe@baylibre.com>
Move all rockchip kconfig in its own subdirectory.
Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
---
drivers/crypto/Kconfig | 32 ++------------------------------
drivers/crypto/Makefile | 2 +-
drivers/crypto/rockchip/Kconfig | 28 ++++++++++++++++++++++++++++
3 files changed, 31 insertions(+), 31 deletions(-)
create mode 100644 drivers/crypto/rockchip/Kconfig
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
index 2947888d3b82..96c5b8060db0 100644
--- a/drivers/crypto/Kconfig
+++ b/drivers/crypto/Kconfig
@@ -646,6 +646,8 @@ config CRYPTO_DEV_QCOM_RNG
To compile this driver as a module, choose M here. The
module will be called qcom-rng. If unsure, say N.
+source "drivers/crypto/rockchip/Kconfig"
+
config CRYPTO_DEV_VMX
bool "Support for VMX cryptographic acceleration instructions"
depends on PPC64 && VSX
@@ -666,36 +668,6 @@ config CRYPTO_DEV_IMGTEC_HASH
hardware hash accelerator. Supporting MD5/SHA1/SHA224/SHA256
hashing algorithms.
-config CRYPTO_DEV_ROCKCHIP
- tristate "Rockchip's Cryptographic Engine driver"
- depends on OF && ARCH_ROCKCHIP
- depends on PM
- select CRYPTO_ECB
- select CRYPTO_CBC
- select CRYPTO_DES
- select CRYPTO_AES
- select CRYPTO_ENGINE
- select CRYPTO_LIB_DES
- select CRYPTO_MD5
- select CRYPTO_SHA1
- select CRYPTO_SHA256
- select CRYPTO_HASH
- select CRYPTO_SKCIPHER
-
- help
- This driver interfaces with the hardware crypto accelerator.
- Supporting cbc/ecb chainmode, and aes/des/des3_ede cipher mode.
-
-config CRYPTO_DEV_ROCKCHIP_DEBUG
- bool "Enable Rockchip crypto stats"
- depends on CRYPTO_DEV_ROCKCHIP
- depends on DEBUG_FS
- help
- Say y to enable Rockchip crypto debug stats.
- This will create /sys/kernel/debug/rk3288_crypto/stats for displaying
- the number of requests per algorithm and other internal stats.
-
-
config CRYPTO_DEV_ZYNQMP_AES
tristate "Support for Xilinx ZynqMP AES hw accelerator"
depends on ZYNQMP_FIRMWARE || COMPILE_TEST
diff --git a/drivers/crypto/Makefile b/drivers/crypto/Makefile
index 116de173a66c..7a9c627a09c6 100644
--- a/drivers/crypto/Makefile
+++ b/drivers/crypto/Makefile
@@ -36,7 +36,7 @@ obj-$(CONFIG_CRYPTO_DEV_PPC4XX) += amcc/
obj-$(CONFIG_CRYPTO_DEV_QAT) += qat/
obj-$(CONFIG_CRYPTO_DEV_QCE) += qce/
obj-$(CONFIG_CRYPTO_DEV_QCOM_RNG) += qcom-rng.o
-obj-$(CONFIG_CRYPTO_DEV_ROCKCHIP) += rockchip/
+obj-y += rockchip/
obj-$(CONFIG_CRYPTO_DEV_S5P) += s5p-sss.o
obj-$(CONFIG_CRYPTO_DEV_SA2UL) += sa2ul.o
obj-$(CONFIG_CRYPTO_DEV_SAHARA) += sahara.o
diff --git a/drivers/crypto/rockchip/Kconfig b/drivers/crypto/rockchip/Kconfig
new file mode 100644
index 000000000000..1010d897d9ef
--- /dev/null
+++ b/drivers/crypto/rockchip/Kconfig
@@ -0,0 +1,28 @@
+config CRYPTO_DEV_ROCKCHIP
+ tristate "Rockchip's Cryptographic Engine driver"
+ depends on OF && ARCH_ROCKCHIP
+ depends on PM
+ select CRYPTO_ECB
+ select CRYPTO_CBC
+ select CRYPTO_DES
+ select CRYPTO_AES
+ select CRYPTO_ENGINE
+ select CRYPTO_LIB_DES
+ select CRYPTO_MD5
+ select CRYPTO_SHA1
+ select CRYPTO_SHA256
+ select CRYPTO_HASH
+ select CRYPTO_SKCIPHER
+
+ help
+ This driver interfaces with the hardware crypto accelerator.
+ Supporting cbc/ecb chainmode, and aes/des/des3_ede cipher mode.
+
+config CRYPTO_DEV_ROCKCHIP_DEBUG
+ bool "Enable Rockchip crypto stats"
+ depends on CRYPTO_DEV_ROCKCHIP
+ depends on DEBUG_FS
+ help
+ Say y to enable Rockchip crypto debug stats.
+ This will create /sys/kernel/debug/rk3288_crypto/stats for displaying
+ the number of requests per algorithm and other internal stats.
--
2.35.1
next prev parent reply other threads:[~2022-09-27 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 8:00 [PATCH RFT 0/5] crypto: rockchip: add crypto offloader V2 Corentin Labbe
2022-09-27 8:00 ` Corentin Labbe [this message]
2022-09-27 8:00 ` [PATCH RFT 2/5] dt-bindings: crypto: add support for rockchip,crypto-rk3588 Corentin Labbe
2022-09-29 22:15 ` Rob Herring
2022-09-27 8:00 ` [PATCH RFT 3/5] MAINTAINERS: add new dt-binding doc to the right entry Corentin Labbe
2022-09-27 8:00 ` [PATCH RFT 4/5] crypto: rockchip: support the new crypto IP for rk3568/rk3588 Corentin Labbe
2022-09-27 21:39 ` Aurelien Jarno
2022-09-29 7:33 ` LABBE Corentin
2022-10-07 4:53 ` Shengyu Qu
2022-09-27 8:00 ` [PATCH RFT 5/5] ARM64: dts: rk3568: add crypto node Corentin Labbe
2022-09-27 21:34 ` [PATCH RFT 0/5] crypto: rockchip: add crypto offloader V2 Aurelien Jarno
2022-09-29 7:33 ` LABBE Corentin
2022-09-29 20:33 ` Aurelien Jarno
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=20220927080048.3151911-2-clabbe@baylibre.com \
--to=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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®