From: wen.ping.teh@intel.com
To: herbert@gondor.apana.org.au, davem@davemloft.net,
catalin.marinas@arm.com, will@kernel.org,
bjorn.andersson@linaro.org, shawnguo@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dmitry.baryshkov@linaro.org
Cc: dinguyen@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
Teh Wen Ping <wen.ping.teh@intel.com>
Subject: [PATCH 0/2] crypto: intel-fcs: Add crypto service driver for Intel SoCFPGA
Date: Wed, 14 Sep 2022 22:41:37 +0800 [thread overview]
Message-ID: <20220914144137.605279-1-wen.ping.teh@intel.com> (raw)
From: Teh Wen Ping <wen.ping.teh@intel.com>
This patch introduces a crypto service driver for Intel SoCFPGA
family. The FPGA Crypto Service (FCS) includes a large set of security
features that are provided by the Secure Device Manager(SDM) in FPGA.
The driver provide IOCTL interface for user to call the crypto services
and send them to SDM's mailbox.
Teh Wen Ping (2):
crypto: intel-fcs: crypto service driver for Intel SoCFPGA family
arm64: defconfig: add CRYPTO_DEV_INTEL_FCS
arch/arm64/configs/defconfig | 1 +
drivers/crypto/Kconfig | 11 +
drivers/crypto/Makefile | 1 +
drivers/crypto/intel_fcs.c | 726 +++++++++++++++++++++++++++
include/uapi/linux/intel_fcs-ioctl.h | 211 ++++++++
5 files changed, 950 insertions(+)
create mode 100644 drivers/crypto/intel_fcs.c
create mode 100644 include/uapi/linux/intel_fcs-ioctl.h
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-09-14 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 14:41 wen.ping.teh [this message]
2022-09-15 3:25 ` [PATCH 0/2] crypto: intel-fcs: Add crypto service driver for Intel SoCFPGA wen.ping.teh
2022-09-15 11:46 ` Dmitry Baryshkov
2022-09-15 13:52 ` wen.ping.teh
2022-09-15 14:42 ` Dmitry Baryshkov
2022-09-29 4:16 ` wen.ping.teh
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=20220914144137.605279-1-wen.ping.teh@intel.com \
--to=wen.ping.teh@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=dinguyen@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--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=shawnguo@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).