From: Weili Qian <qianweili@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<wangzhou1@hisilicon.com>, <liulongfang@huawei.com>
Subject: [PATCH v2 0/5] crypto: hisilicon - support runtime PM for accelerator devices
Date: Fri, 13 Aug 2021 17:50:04 +0800 [thread overview]
Message-ID: <1628848209-26398-1-git-send-email-qianweili@huawei.com> (raw)
Kunpeng930 accelerator devices support runtime power management, this
patchset enables runtime PM for accelerator devices.
---
v1->v2: fix warning
---
Weili Qian (5):
crypto: hisilicon - using 'debugfs_create_file' instead of
'debugfs_create_regset32'
crypto: hisilicon - add runtime PM ops
crypto: hisilicon - support runtime PM for accelerator device
crypto: hisilicon - change parameter passing of debugfs function
crypto: hisilicon - check _PS0 and _PR0 method
drivers/crypto/hisilicon/hpre/hpre_main.c | 60 ++++-
drivers/crypto/hisilicon/qm.c | 430 +++++++++++++++++++++++++-----
drivers/crypto/hisilicon/qm.h | 8 +
drivers/crypto/hisilicon/sec2/sec_main.c | 58 +++-
drivers/crypto/hisilicon/zip/zip_main.c | 57 +++-
5 files changed, 521 insertions(+), 92 deletions(-)
--
2.8.1
next reply other threads:[~2021-08-13 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 9:50 Weili Qian [this message]
2021-08-13 9:50 ` [PATCH v2 1/5] crypto: hisilicon - using 'debugfs_create_file' instead of 'debugfs_create_regset32' Weili Qian
2021-08-13 9:50 ` [PATCH v2 2/5] crypto: hisilicon - add runtime PM ops Weili Qian
2021-08-13 9:50 ` [PATCH v2 3/5] crypto: hisilicon - support runtime PM for accelerator device Weili Qian
2021-08-13 9:50 ` [PATCH v2 4/5] crypto: hisilicon - change parameter passing of debugfs function Weili Qian
2021-08-13 9:50 ` [PATCH v2 5/5] crypto: hisilicon - check _PS0 and _PR0 method Weili Qian
2021-08-21 7:50 ` [PATCH v2 0/5] crypto: hisilicon - support runtime PM for accelerator devices 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=1628848209-26398-1-git-send-email-qianweili@huawei.com \
--to=qianweili@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=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).