From: Harsha <harsha.harsha@xilinx.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<michals@xilinx.com>, <linux-arm-kernel@lists.infradead.org>,
<robh+dt@kernel.org>, <devicetree@vger.kernel.org>
Cc: <saratcha@xilinx.com>, <harshj@xilinx.com>, <git@xilinx.com>,
Harsha <harsha.harsha@xilinx.com>
Subject: [PATCH 0/4] crypto: Add Xilinx ZynqMP SHA3 driver support
Date: Sun, 23 Jan 2022 15:17:03 +0530 [thread overview]
Message-ID: <1642931227-20706-1-git-send-email-harsha.harsha@xilinx.com> (raw)
This patch set does the following:
- Updates the Makefile for xilinx subdirectory
- Adds communication layer support for sha_hash in zynqmp.c
- Adds Xilinx ZynqMP driver for SHA3 Algorithm
- Updates the list of MAINTAINERS
Harsha (4):
drivers: crypto: Updated Makefile for xilinx subdirectory
firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality
crypto: xilinx: Add Xilinx SHA3 driver
MAINTAINERS: Add maintainer for Xilinx ZynqMP SHA3 driver
MAINTAINERS | 5 +
drivers/crypto/Kconfig | 10 ++
drivers/crypto/Makefile | 2 +-
drivers/crypto/xilinx/Makefile | 1 +
drivers/crypto/xilinx/zynqmp-sha.c | 285 +++++++++++++++++++++++++++++++++++
drivers/firmware/xilinx/zynqmp.c | 26 ++++
include/linux/firmware/xlnx-zynqmp.h | 8 +
7 files changed, 336 insertions(+), 1 deletion(-)
create mode 100644 drivers/crypto/xilinx/zynqmp-sha.c
--
1.8.2.1
next reply other threads:[~2022-01-23 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 9:47 Harsha [this message]
2022-01-23 9:47 ` [PATCH 1/4] drivers: crypto: Updated Makefile for xilinx subdirectory Harsha
2022-01-23 9:47 ` [PATCH 2/4] firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality Harsha
2022-01-23 9:47 ` [PATCH 3/4] crypto: xilinx: Add Xilinx SHA3 driver Harsha
2022-01-24 19:24 ` kernel test robot
2022-01-23 9:47 ` [PATCH 4/4] MAINTAINERS: Add maintainer for Xilinx ZynqMP " 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=1642931227-20706-1-git-send-email-harsha.harsha@xilinx.com \
--to=harsha.harsha@xilinx.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=harshj@xilinx.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=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).