From: Harsha Harsha <harsha.harsha@amd.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <michals@xilinx.com>
Cc: <saratcha@xilinx.com>, <git@amd.com>,
Harsha Harsha <harsha.harsha@amd.com>
Subject: [PATCH 0/4] crypto: Add Xilinx ZynqMP RSA driver support
Date: Sat, 18 Feb 2023 11:08:05 +0530 [thread overview]
Message-ID: <20230218053809.1780-1-harsha.harsha@amd.com> (raw)
This patch set does the following:
- Get the SoC family specific data for crypto operation
- Adds communication layer support for zynqmp_pm_rsa in zynqmp.c
- Adds Xilinx driver for RSA Algorithm
- Updates the list of MAINTAINERS
Harsha Harsha (4):
firmware: xilinx: Get the SoC family specific data for crypto
operation
firmware: xilinx: Add ZynqMP RSA API for RSA encrypt/decrypt operation
crypto: xilinx: Add ZynqMP RSA driver
MAINTAINERS: Add maintainer for Xilinx ZynqMP RSA driver
MAINTAINERS | 5 +
drivers/crypto/Kconfig | 10 +
drivers/crypto/xilinx/Makefile | 1 +
drivers/crypto/xilinx/xilinx-rsa.c | 489 +++++++++++++++++++++++++++
drivers/firmware/xilinx/zynqmp.c | 100 ++++++
include/linux/firmware/xlnx-zynqmp.h | 42 +++
6 files changed, 647 insertions(+)
create mode 100644 drivers/crypto/xilinx/xilinx-rsa.c
--
2.36.1
next reply other threads:[~2023-02-18 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 5:38 Harsha Harsha [this message]
2023-02-18 5:38 ` [PATCH 1/4] firmware: xilinx: Get the SoC family specific data for crypto operation Harsha Harsha
2023-02-18 5:38 ` [PATCH 2/4] firmware: xilinx: Add ZynqMP RSA API for RSA encrypt/decrypt operation Harsha Harsha
2023-02-18 5:38 ` [PATCH 3/4] crypto: xilinx: Add ZynqMP RSA driver Harsha Harsha
2023-03-10 10:31 ` Herbert Xu
2023-03-15 5:02 ` Harsha, Harsha
2023-03-15 5:06 ` Herbert Xu
2023-02-18 5:38 ` [PATCH 4/4] MAINTAINERS: Add maintainer for Xilinx " Harsha Harsha
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=20230218053809.1780-1-harsha.harsha@amd.com \
--to=harsha.harsha@amd.com \
--cc=davem@davemloft.net \
--cc=git@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=saratcha@xilinx.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®