From: Heiko Stuebner <heiko@sntech.de>
To: palmer@rivosinc.com
Cc: greentime.hu@sifive.com, conor@kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
christoph.muellner@vrull.eu, heiko@sntech.de,
Heiko Stuebner <heiko.stuebner@vrull.eu>
Subject: [PATCH RFC v2 05/16] RISC-V: hook new crypto subdir into build-system
Date: Tue, 28 Feb 2023 01:05:33 +0100 [thread overview]
Message-ID: <20230228000544.2234136-6-heiko@sntech.de> (raw)
In-Reply-To: <20230228000544.2234136-1-heiko@sntech.de>
From: Heiko Stuebner <heiko.stuebner@vrull.eu>
Create a crypto subdirectory for added accelerated cryptography routines
and hook it into the riscv Kbuild and the main crypto Kconfig.
Signed-off-by: Heiko Stuebner <heiko.stuebner@vrull.eu>
---
arch/riscv/Kbuild | 1 +
arch/riscv/crypto/Kconfig | 5 +++++
arch/riscv/crypto/Makefile | 4 ++++
crypto/Kconfig | 3 +++
4 files changed, 13 insertions(+)
create mode 100644 arch/riscv/crypto/Kconfig
create mode 100644 arch/riscv/crypto/Makefile
diff --git a/arch/riscv/Kbuild b/arch/riscv/Kbuild
index afa83e307a2e..250d1fd38618 100644
--- a/arch/riscv/Kbuild
+++ b/arch/riscv/Kbuild
@@ -2,6 +2,7 @@
obj-y += kernel/ mm/ net/
obj-$(CONFIG_BUILTIN_DTB) += boot/dts/
+obj-$(CONFIG_CRYPTO) += crypto/
obj-y += errata/
obj-$(CONFIG_KVM) += kvm/
diff --git a/arch/riscv/crypto/Kconfig b/arch/riscv/crypto/Kconfig
new file mode 100644
index 000000000000..10d60edc0110
--- /dev/null
+++ b/arch/riscv/crypto/Kconfig
@@ -0,0 +1,5 @@
+# SPDX-License-Identifier: GPL-2.0
+
+menu "Accelerated Cryptographic Algorithms for CPU (riscv)"
+
+endmenu
diff --git a/arch/riscv/crypto/Makefile b/arch/riscv/crypto/Makefile
new file mode 100644
index 000000000000..b3b6332c9f6d
--- /dev/null
+++ b/arch/riscv/crypto/Makefile
@@ -0,0 +1,4 @@
+# SPDX-License-Identifier: GPL-2.0-only
+#
+# linux/arch/riscv/crypto/Makefile
+#
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 9c86f7045157..003921cb0301 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -1401,6 +1401,9 @@ endif
if PPC
source "arch/powerpc/crypto/Kconfig"
endif
+if RISCV
+source "arch/riscv/crypto/Kconfig"
+endif
if S390
source "arch/s390/crypto/Kconfig"
endif
--
2.39.0
next prev parent reply other threads:[~2023-02-28 0:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 0:05 [PATCH RFC v2 00/16] RISC-V: support some cryptography accelerations Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 01/16] riscv: Add support for kernel mode vector Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 02/16] riscv: Add vector extension XOR implementation Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 03/16] RISC-V: add Zbc extension detection Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 04/16] RISC-V: add Zbkb " Heiko Stuebner
2023-02-28 0:05 ` Heiko Stuebner [this message]
2023-02-28 0:05 ` [PATCH RFC v2 06/16] RISC-V: crypto: add accelerated GCM GHASH implementation Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 07/16] RISC-V: add helper function to read the vector VLEN Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 08/16] RISC-V: add vector crypto extension detection Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 09/16] RISC-V: crypto: update perl include with helpers for vector (crypto) instructions Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 10/16] RISC-V: crypto: add Zvkb accelerated GCM GHASH implementation Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 11/16] RISC-V: crypto: add Zvkg " Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 12/16] RISC-V: crypto: add a vector-crypto-accelerated SHA256 implementation Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 13/16] RISC-V: crypto: add a vector-crypto-accelerated SHA512 implementation Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 14/16] RISC-V: crypto: add Zvkned accelerated AES encryption implementation Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 15/16] RISC-V: crypto: add Zvksed accelerated SM4 " Heiko Stuebner
2023-02-28 0:05 ` [PATCH RFC v2 16/16] RISC-V: crypto: add Zvksh accelerated SM3 hash implementation Heiko Stuebner
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=20230228000544.2234136-6-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=christoph.muellner@vrull.eu \
--cc=conor@kernel.org \
--cc=greentime.hu@sifive.com \
--cc=heiko.stuebner@vrull.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
/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®