From: Herbert Xu <herbert@gondor.apana.org.au>
To: Wojciech Ziemba <wojciech.ziemba@intel.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
qat-linux@intel.com
Subject: Re: [PATCH v2 0/3] Introduce support for QAT Dynamic Power Management
Date: Fri, 18 Feb 2022 16:37:31 +1100 [thread overview]
Message-ID: <Yg8wmyvL2f/UZJbu@gondor.apana.org.au> (raw)
In-Reply-To: <20220210133827.2366901-1-wojciech.ziemba@intel.com>
On Thu, Feb 10, 2022 at 01:38:24PM +0000, Wojciech Ziemba wrote:
> This patch set consist of following updates:
> 1. Add misc workqueue for general purpose usage.
> 2. Move error source related CSRs from 4xxx to the wider GEN4 header
> file.
> 3. Add support for HW QAT Power Management (PM) feature.
> This feature is enabled at init time (1) by sending an admin
> message to
> the firmware, targeting the admin AE, that sets the idle time
> before
> the device changes state and (2) by unmasking the PM source of
> interrupt in ERRMSK2.
>
> The interrupt handler is extended to handle a PM interrupt which
> is triggered by HW when a PM transition occurs. In this case,
> the
> driver responds acknowledging the transaction using the HOST_MSG
> mailbox.
>
> Changes since v1:
> - Moved unmasking PM interrupts after PM interrupt source enable to
> avoid a spurious interrupt
> - Fixed kbuild bot issue by moving adf_handle_pm_int() out of
> CONFIG_PCI_IOV scope
> - Rename [..]_init_pm() functions to [..]_enable_pm() as the function
> needs to be called inside adf_start()
>
>
> Wojciech Ziemba (3):
> crypto: qat - add misc workqueue
> crypto: qat - move and rename GEN4 error register definitions
> crypto: qat - enable power management for QAT GEN4
>
> .../crypto/qat/qat_4xxx/adf_4xxx_hw_data.c | 21 +--
> .../crypto/qat/qat_4xxx/adf_4xxx_hw_data.h | 24 ---
> drivers/crypto/qat/qat_common/Makefile | 1 +
> .../crypto/qat/qat_common/adf_accel_devices.h | 2 +
> drivers/crypto/qat/qat_common/adf_admin.c | 37 +++++
> .../crypto/qat/qat_common/adf_common_drv.h | 4 +
> drivers/crypto/qat/qat_common/adf_ctl_drv.c | 6 +
> .../crypto/qat/qat_common/adf_gen4_hw_data.h | 14 ++
> drivers/crypto/qat/qat_common/adf_gen4_pm.c | 137 ++++++++++++++++++
> drivers/crypto/qat/qat_common/adf_gen4_pm.h | 44 ++++++
> drivers/crypto/qat/qat_common/adf_init.c | 6 +
> drivers/crypto/qat/qat_common/adf_isr.c | 42 ++++++
> .../qat/qat_common/icp_qat_fw_init_admin.h | 1 +
> 13 files changed, 306 insertions(+), 33 deletions(-)
> create mode 100644 drivers/crypto/qat/qat_common/adf_gen4_pm.c
> create mode 100644 drivers/crypto/qat/qat_common/adf_gen4_pm.h
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2022-02-18 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:38 [PATCH v2 0/3] Introduce support for QAT Dynamic Power Management Wojciech Ziemba
2022-02-10 13:38 ` [PATCH v2 1/3] crypto: qat - add misc workqueue Wojciech Ziemba
2022-02-10 13:38 ` [PATCH v2 2/3] crypto: qat - move and rename GEN4 error register definitions Wojciech Ziemba
2022-02-10 13:38 ` [PATCH v2 3/3] crypto: qat - enable power management for QAT GEN4 Wojciech Ziemba
2022-02-18 5:37 ` Herbert Xu [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=Yg8wmyvL2f/UZJbu@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=wojciech.ziemba@intel.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).