From: Zhou Wang <wangzhou1@hisilicon.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH 0/4] crypto: hisilicon: Add HiSilicon QM and ZIP controller driver
Date: Thu, 10 Jan 2019 14:30:26 +0800 [thread overview]
Message-ID: <5C36E682.9040701@hisilicon.com> (raw)
In-Reply-To: <1545465105-133138-1-git-send-email-wangzhou1@hisilicon.com>
On 2018/12/22 15:51, Zhou Wang wrote:
> This series adds HiSilicon QM and ZIP controller driver in crypto subsystem.
>
> A simple QM/ZIP driver which helps to provide an example for a general
> accelerator framework is under review in community[1]. Based on this simple
> driver, this series adds HW v2 support, PCI passthrough, reset, PCI/misc error
> handler, debug support. But unlike [1], driver in this patchset only registers
> to crypto subsystem.
>
> There will be a long discussion about above accelerator framework in the
> process of upstreaming. So let's firstly review and upstream QM/ZIP crypto
> driver.
>
> References:
> [1] https://lkml.org/lkml/2018/11/12/1951
>
> Zhou Wang (4):
> Documentation: Add debugfs doc for hisi_zip
> crypto: hisilicon: Add queue management driver for HiSilicon QM module
> crypto: hisilicon: Add HiSilicon ZIP accelerator support
> MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver
>
> Documentation/ABI/testing/debugfs-hisi-zip | 50 +
> MAINTAINERS | 8 +
> drivers/crypto/hisilicon/Kconfig | 11 +
> drivers/crypto/hisilicon/Makefile | 2 +
> drivers/crypto/hisilicon/qm.c | 1823 ++++++++++++++++++++++++++++
> drivers/crypto/hisilicon/qm.h | 177 +++
> drivers/crypto/hisilicon/zip/Makefile | 2 +
> drivers/crypto/hisilicon/zip/zip.h | 60 +
> drivers/crypto/hisilicon/zip/zip_crypto.c | 410 +++++++
> drivers/crypto/hisilicon/zip/zip_main.c | 1161 ++++++++++++++++++
> 10 files changed, 3704 insertions(+)
> create mode 100644 Documentation/ABI/testing/debugfs-hisi-zip
> create mode 100644 drivers/crypto/hisilicon/qm.c
> create mode 100644 drivers/crypto/hisilicon/qm.h
> create mode 100644 drivers/crypto/hisilicon/zip/Makefile
> create mode 100644 drivers/crypto/hisilicon/zip/zip.h
> create mode 100644 drivers/crypto/hisilicon/zip/zip_crypto.c
> create mode 100644 drivers/crypto/hisilicon/zip/zip_main.c
>
Any comments about this series?
Best,
Zhou
prev parent reply other threads:[~2019-01-10 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 7:51 [PATCH 0/4] crypto: hisilicon: Add HiSilicon QM and ZIP controller driver Zhou Wang
2018-12-22 7:51 ` [PATCH 1/4] Documentation: Add debugfs doc for hisi_zip Zhou Wang
2018-12-22 7:51 ` [PATCH 2/4] crypto: hisilicon: Add queue management driver for HiSilicon QM module Zhou Wang
2018-12-22 7:51 ` [PATCH 3/4] crypto: hisilicon: Add HiSilicon ZIP accelerator support Zhou Wang
2019-01-11 6:08 ` Herbert Xu
2019-01-11 6:34 ` Zhou Wang
2019-01-16 14:12 ` Zhou Wang
2019-01-18 4:55 ` Herbert Xu
2019-01-18 7:55 ` Zhou Wang
2019-01-18 10:09 ` Herbert Xu
2018-12-22 7:51 ` [PATCH 4/4] MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver Zhou Wang
2019-01-10 6:30 ` Zhou Wang [this message]
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=5C36E682.9040701@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.