Linux cryptographic layer development
 help / color / mirror / Atom feed
From: nitesh.venkatesh@intel.com
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com,
	Nitesh Venkatesh <nitesh.venkatesh@intel.com>
Subject: [PATCH 0/2] crypto: qat - fix KPT disable and clarify ABI
Date: Mon, 31 Aug 2026 06:32:32 +0000	[thread overview]
Message-ID: <20260831063355.668528-1-nitesh.venkatesh@intel.com> (raw)

From: Nitesh Venkatesh <nitesh.venkatesh@intel.com>

This small series fixes a recoverability issue in the QAT KPT (Key
Protection Technology) sysfs interface.

Patch 1 fixes the KPT enable sysfs attribute so that '0' writes are
always accepted when the device is down. The asym-service check
previously rejected disable writes when the service was not 'asym',
leaving KPT reported as enabled after switching services.

Patch 2 documents that the device must be in the down state before
the KPT enable attribute can be changed.

Nitesh Venkatesh (2):
  crypto: qat - allow KPT disable when service is not asym
  Documentation: qat: clarify KPT enable device-state requirement

 .../ABI/testing/sysfs-driver-qat_kpt          |  3 ++-
 .../intel/qat/qat_common/adf_sysfs_kpt.c      | 24 ++++++++++++-------
 2 files changed, 18 insertions(+), 9 deletions(-)


base-commit: 6f440283743bd408bfe95a3d1f77aac559130e39
-- 
2.52.0


             reply	other threads:[~2026-08-31  6:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  6:32 nitesh.venkatesh [this message]
2026-08-31  6:32 ` [PATCH 1/2] crypto: qat - allow KPT disable when service is not asym nitesh.venkatesh
2026-08-31  6:32 ` [PATCH 2/2] Documentation: qat: clarify KPT enable device-state requirement nitesh.venkatesh

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=20260831063355.668528-1-nitesh.venkatesh@intel.com \
    --to=nitesh.venkatesh@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=qat-linux@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