From: Jia Jie Ho <jiajie.ho@starfivetech.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
Vinod Koul <vkoul@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: [PATCH v3 0/6] crypto: starfive: Add support for JH8100
Date: Wed, 28 Feb 2024 00:37:52 +0800 [thread overview]
Message-ID: <20240227163758.198133-1-jiajie.ho@starfivetech.com> (raw)
This patch series add driver support for StarFive JH8100 SoC crypto
engine. Patch 1 adds compatible string and update irq descriptions for
JH8100 device. Subsequent patches update current driver implementations
to support both 7110 and 8100 variants.
v2->v3:
- Use of device data instead of #ifdef CONFIG_ for different device
variants.
- Updated dt bindings compatible and interrupts descriptions.
- Added patch 4 to support hardware quirks for dw-axi-dmac driver.
v1->v2:
- Resolved build warnings reported by kernel test robot
https://lore.kernel.org/oe-kbuild-all/202312170614.24rtwf9x-lkp@intel.com/
Jia Jie Ho (6):
dt-bindings: crypto: starfive: Add jh8100 support
crypto: starfive: Update hash dma usage
crypto: starfive: Use dma for aes requests
dmaengine: dw-axi-dmac: Support hardware quirks
crypto: starfive: Add sm3 support for JH8100
crypto: starfive: Add sm4 support for JH8100
.../crypto/starfive,jh7110-crypto.yaml | 30 +-
drivers/crypto/starfive/Kconfig | 30 +-
drivers/crypto/starfive/Makefile | 5 +-
drivers/crypto/starfive/jh7110-aes.c | 592 ++++++---
drivers/crypto/starfive/jh7110-cryp.c | 77 +-
drivers/crypto/starfive/jh7110-cryp.h | 112 +-
drivers/crypto/starfive/jh7110-hash.c | 304 ++---
drivers/crypto/starfive/jh8100-sm3.c | 535 ++++++++
drivers/crypto/starfive/jh8100-sm4.c | 1119 +++++++++++++++++
.../dma/dw-axi-dmac/dw-axi-dmac-platform.c | 32 +-
drivers/dma/dw-axi-dmac/dw-axi-dmac.h | 2 +
include/linux/dma/dw_axi.h | 11 +
12 files changed, 2412 insertions(+), 437 deletions(-)
create mode 100644 drivers/crypto/starfive/jh8100-sm3.c
create mode 100644 drivers/crypto/starfive/jh8100-sm4.c
create mode 100644 include/linux/dma/dw_axi.h
--
2.34.1
next reply other threads:[~2024-02-27 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 16:37 Jia Jie Ho [this message]
2024-02-27 16:37 ` [PATCH v3 1/6] dt-bindings: crypto: starfive: Add jh8100 support Jia Jie Ho
2024-02-28 11:19 ` Conor Dooley
2024-02-28 15:51 ` Rob Herring
2024-02-29 2:17 ` JiaJie Ho
2024-02-27 16:37 ` [PATCH v3 2/6] crypto: starfive: Update hash dma usage Jia Jie Ho
2024-02-27 16:37 ` [PATCH v3 3/6] crypto: starfive: Use dma for aes requests Jia Jie Ho
2024-02-27 16:37 ` [PATCH v3 4/6] dmaengine: dw-axi-dmac: Support hardware quirks Jia Jie Ho
2024-02-27 16:37 ` [PATCH v3 5/6] crypto: starfive: Add sm3 support for JH8100 Jia Jie Ho
2024-02-27 16:37 ` [PATCH v3 6/6] crypto: starfive: Add sm4 " Jia Jie Ho
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=20240227163758.198133-1-jiajie.ho@starfivetech.com \
--to=jiajie.ho@starfivetech.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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®