From: Kai Ye <yekai13@huawei.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yekai13@huawei.com>
Subject: [PATCH 0/3] crypto: hisilicon/qm - reconstruct and optimize the debugfs code
Date: Sat, 29 Oct 2022 09:47:58 +0000 [thread overview]
Message-ID: <20221029094801.43843-1-yekai13@huawei.com> (raw)
Split a debugfs.c from qm to reduce the qm code complexity. And optimize the
process of the command dumping. Some optimizations on command dumping in
debugfs.c file code.
Kai Ye (3):
crypto: hisilicon/qm - modify the process of regs dfx
crypto: hisilicon/qm - split a debugfs.c from qm
crypto: hisilicon/qm - the command dump process is modified
drivers/crypto/hisilicon/Makefile | 2 +-
drivers/crypto/hisilicon/debugfs.c | 1173 ++++++++++++++++++
drivers/crypto/hisilicon/hpre/hpre_main.c | 6 +-
drivers/crypto/hisilicon/qm.c | 1360 ++-------------------
drivers/crypto/hisilicon/qm_common.h | 87 ++
drivers/crypto/hisilicon/sec2/sec_main.c | 6 +-
drivers/crypto/hisilicon/zip/zip_main.c | 6 +-
include/linux/hisi_acc_qm.h | 8 +-
8 files changed, 1382 insertions(+), 1266 deletions(-)
create mode 100644 drivers/crypto/hisilicon/debugfs.c
create mode 100644 drivers/crypto/hisilicon/qm_common.h
--
2.17.1
next reply other threads:[~2022-10-29 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 9:47 Kai Ye [this message]
2022-10-29 9:47 ` [PATCH 1/3] crypto: hisilicon/qm - modify the process of regs dfx Kai Ye
2022-11-04 9:05 ` Herbert Xu
2022-11-04 10:07 ` yekai (A)
2022-11-05 1:39 ` yekai (A)
2022-11-05 2:45 ` Herbert Xu
2022-10-29 9:48 ` [PATCH 2/3] crypto: hisilicon/qm - split a debugfs.c from qm Kai Ye
2022-10-29 9:48 ` [PATCH 3/3] crypto: hisilicon/qm - the command dump process is modified Kai Ye
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=20221029094801.43843-1-yekai13@huawei.com \
--to=yekai13@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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