From: Kai Ye <yekai13@huawei.com>
To: <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<wangzhou1@hisilicon.com>, <yekai13@huawei.com>,
<liulongfang@huawei.com>
Subject: [PATCH 05/11] Documentation: update debugfs doc for Hisilicon HPRE
Date: Sat, 9 Apr 2022 16:03:22 +0800 [thread overview]
Message-ID: <20220409080328.15783-6-yekai13@huawei.com> (raw)
In-Reply-To: <20220409080328.15783-1-yekai13@huawei.com>
Update documentation describing DebugFS that could help
to check the change of register values.
Signed-off-by: Kai Ye <yekai13@huawei.com>
---
Documentation/ABI/testing/debugfs-hisi-hpre | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/Documentation/ABI/testing/debugfs-hisi-hpre b/Documentation/ABI/testing/debugfs-hisi-hpre
index 396de7bc735d..82abf92df429 100644
--- a/Documentation/ABI/testing/debugfs-hisi-hpre
+++ b/Documentation/ABI/testing/debugfs-hisi-hpre
@@ -104,6 +104,20 @@ Description: Dump the status of the QM.
Four states: initiated, started, stopped and closed.
Available for both PF and VF, and take no other effect on HPRE.
+What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/diff_regs
+Date: Mar 2022
+Contact: linux-crypto@vger.kernel.org
+Description: QM debug registers(regs) read hardware register value. This
+ node is used to show the change of the qm register values. This
+ node can be help users to check the change of register values.
+
+What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/diff_regs
+Date: Mar 2022
+Contact: linux-crypto@vger.kernel.org
+Description: HPRE debug registers(regs) read hardware register value. This
+ node is used to show the change of the register values. This
+ node can be help users to check the change of register values.
+
What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_cnt
Date: Apr 2020
Contact: linux-crypto@vger.kernel.org
--
2.33.0
next prev parent reply other threads:[~2022-04-09 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 8:03 [PATCH 00/11] add regitser checking and last word dumping for ACC Kai Ye
2022-04-09 8:03 ` [PATCH 01/11] crypto: hisilicon/qm - add register checking " Kai Ye
2022-04-09 8:03 ` [PATCH 02/11] crypto: hisilicon/hpre - support register checking Kai Ye
2022-04-09 8:03 ` [PATCH 03/11] crypto: hisilicon/sec " Kai Ye
2022-04-09 8:03 ` [PATCH 04/11] crypto: hisilicon/zip " Kai Ye
2022-04-09 8:03 ` Kai Ye [this message]
2022-04-09 8:03 ` [PATCH 06/11] Documentation: update debugfs doc for Hisilicon SEC Kai Ye
2022-04-09 8:03 ` [PATCH 07/11] Documentation: update debugfs doc for Hisilicon ZIP Kai Ye
2022-04-09 8:03 ` [PATCH 08/11] crypto: hisilicon/qm - add last word dumping for ACC Kai Ye
2022-04-09 8:03 ` [PATCH 09/11] crypto: hisilicon/sec - support last word dumping Kai Ye
2022-04-09 8:03 ` [PATCH 10/11] crypto: hisilicon/hpre " Kai Ye
2022-04-09 8:03 ` [PATCH 11/11] crypto: hisilicon/zip " Kai Ye
2022-04-15 8:40 ` [PATCH 00/11] add regitser checking and last word dumping for ACC 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=20220409080328.15783-6-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 \
--cc=liulongfang@huawei.com \
--cc=wangzhou1@hisilicon.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).