From: Alexey Kardashevskiy <aik@amd.com>
To: <x86@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
"Ashish Kalra" <ashish.kalra@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, "Lukas Wunner" <lukas@wunner.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>,
<linux-coco@lists.linux.dev>,
"Santosh Shukla" <santosh.shukla@amd.com>,
"Pratik R . Sampat" <prsampat@amd.com>,
Scott Soule Cheloha <scott.cheloha@amd.com>,
Ackerley Tng <ackerleytng@google.com>,
Sean Christopherson <seanjc@google.com>,
Fuad Tabba <tabba@google.com>,
Xu Yilun <yilun.xu@linux.intel.com>,
Alexey Kardashevskiy <aik@amd.com>, <aik@ozlabs.ru>
Subject: [PATCH kernel 4/4] crypto/ccp/tsm: Use TSM API for DOE
Date: Thu, 19 Nov 2026 23:57:33 +1100 [thread overview]
Message-ID: <20261119125733.1860288-5-aik@amd.com> (raw)
In-Reply-To: <20261119125733.1860288-1-aik@amd.com>
Compared to the currently used pci_doe(), the pci_tsm_doe_transfer() helper
performs a few more sanity checks, use that helper now.
Signed-off-by: Alexey Kardashevskiy <aik@amd.com>
---
drivers/crypto/ccp/sev-dev-tsm.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/ccp/sev-dev-tsm.c b/drivers/crypto/ccp/sev-dev-tsm.c
index eb16948e1561b..70aa26efd6a6c 100644
--- a/drivers/crypto/ccp/sev-dev-tsm.c
+++ b/drivers/crypto/ccp/sev-dev-tsm.c
@@ -39,8 +39,9 @@ static int sev_tio_spdm_cmd(struct tio_dsm *dsm, int ret)
/* ret > 0 means "SPDM requested" */
while (ret == PCI_DOE_FEATURE_CMA || ret == PCI_DOE_FEATURE_SSESSION) {
- ret = pci_doe(dsm->tsm.doe_mb, PCI_VENDOR_ID_PCI_SIG, ret,
- spdm->req, spdm->req_len, spdm->rsp, spdm->rsp_len);
+ ret = pci_tsm_doe_transfer(dsm->tsm.base_tsm.pdev, ret,
+ spdm->req, spdm->req_len,
+ spdm->rsp, spdm->rsp_len);
if (ret < 0)
break;
--
2.55.0
prev parent reply other threads:[~2026-11-19 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 12:57 [PATCH kernel 0/4] PCI/TSM queue Alexey Kardashevskiy
2026-11-19 12:57 ` [PATCH kernel 1/4] MAINTAINERS: Update TSM file coverage and repository Alexey Kardashevskiy
2026-11-19 12:57 ` [PATCH kernel 2/4] crypto/ccp/tsm: Fix potential size mismatch in releasing SPDM buffers Alexey Kardashevskiy
2026-11-19 12:57 ` [PATCH kernel 3/4] crypto/ccp/tsm: Remove unused header Alexey Kardashevskiy
2026-11-19 12:57 ` Alexey Kardashevskiy [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=20261119125733.1860288-5-aik@amd.com \
--to=aik@amd.com \
--cc=ackerleytng@google.com \
--cc=aik@ozlabs.ru \
--cc=aneesh.kumar@kernel.org \
--cc=ashish.kalra@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jgg@ziepe.ca \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=prsampat@amd.com \
--cc=santosh.shukla@amd.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=scott.cheloha@amd.com \
--cc=seanjc@google.com \
--cc=tabba@google.com \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--cc=yilun.xu@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
all inboxes | Powered by JetHome®