From: Hui Tang <tanghui20@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-crypto@vger.kernel.org>, <xuzaibo@huawei.com>,
<wangzhou1@hisilicon.com>, <tanghui20@huawei.com>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] crypto: hisilicon - some updates to adapt Kunpeng930
Date: Thu, 4 Feb 2021 16:59:32 +0800 [thread overview]
Message-ID: <1612429176-28084-1-git-send-email-tanghui20@huawei.com> (raw)
1.Update clusters number for both Kunpeng920 and Kunpeng930.
2.Some bugfixs only on Kunpeng920, so added hardware version wrap.
3.Fix use of 'dma_map_single'.
4.Fix PASID on Kunpeng930.
Hui Tang (2):
crypto: hisilicon/hpre - adapt the number of clusters
crypto: hisilicon/hpre - tiny fix
Weili Qian (2):
crypto:hisilicon/qm - fix use of "dma_map_single"
crypto:hisilicon - PASID fixed on Kupeng 930
drivers/crypto/hisilicon/hpre/hpre.h | 8 ++-
drivers/crypto/hisilicon/hpre/hpre_main.c | 100 +++++++++++++++++++-----------
drivers/crypto/hisilicon/qm.c | 61 +++++++++++-------
drivers/crypto/hisilicon/qm.h | 1 +
drivers/crypto/hisilicon/sec2/sec_main.c | 2 +-
drivers/crypto/hisilicon/zip/zip_main.c | 2 +-
6 files changed, 110 insertions(+), 64 deletions(-)
--
2.8.1
next reply other threads:[~2021-02-04 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 8:59 Hui Tang [this message]
2021-02-04 8:59 ` [PATCH 1/4] crypto: hisilicon/hpre - adapt the number of clusters Hui Tang
2021-02-04 8:59 ` [PATCH 2/4] crypto: hisilicon/hpre - tiny fix Hui Tang
2021-02-04 8:59 ` [PATCH 3/4] crypto: hisilicon/qm - fix use of 'dma_map_single' Hui Tang
2021-02-04 8:59 ` [PATCH 4/4] crypto: hisilicon - PASID fixed on Kunpeng 930 Hui Tang
2021-02-10 7:23 ` [PATCH 0/4] crypto: hisilicon - some updates to adapt Kunpeng930 Herbert Xu
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=1612429176-28084-1-git-send-email-tanghui20@huawei.com \
--to=tanghui20@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=xuzaibo@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 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®