From: Rijo Thomas <Rijo-john.Thomas@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
John Allen <john.allen@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Cc: Rijo Thomas <Rijo-john.Thomas@amd.com>,
Mythri Pandeshwara krishna <mythri.pandeshwarakrishna@amd.com>,
Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH v3 0/2] PSP TEE driver update and bug fixes
Date: Mon, 15 Mar 2021 13:55:27 +0530 [thread overview]
Message-ID: <cover.1615796554.git.Rijo-john.Thomas@amd.com> (raw)
The first patch helps to improve the response time by reducing the
polling time of the tee command status variable.
Second patch is a bug fix to handle multi-threaded use-case.
During testing, race condition was seen due to missing synchronisation
in writes to the TEE ring buffer. This patch helps to resolve that.
v3:
* Fixed checkpatch.pl warning
v2:
* Updated copyright year as a part of code change
Rijo Thomas (2):
crypto: ccp - reduce tee command status polling interval from 5ms to
1ms
crypto: ccp - fix command queuing to TEE ring buffer
drivers/crypto/ccp/tee-dev.c | 57 ++++++++++++++++++++++++------------
drivers/crypto/ccp/tee-dev.h | 20 +++++++++++--
2 files changed, 57 insertions(+), 20 deletions(-)
--
2.17.1
next reply other threads:[~2021-03-15 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 8:25 Rijo Thomas [this message]
2021-03-15 8:25 ` [PATCH v3 1/2] crypto: ccp - reduce tee command status polling interval from 5ms to 1ms Rijo Thomas
2021-03-15 8:25 ` [PATCH v3 2/2] crypto: ccp - fix command queuing to TEE ring buffer Rijo Thomas
2021-03-26 9:29 ` [PATCH v3 0/2] PSP TEE driver update and bug fixes Herbert Xu
2021-04-05 6:40 ` Rijo Thomas
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=cover.1615796554.git.Rijo-john.Thomas@amd.com \
--to=rijo-john.thomas@amd.com \
--cc=Devaraj.Rangasamy@amd.com \
--cc=ard.biesheuvel@linaro.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jens.wiklander@linaro.org \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mythri.pandeshwarakrishna@amd.com \
--cc=thomas.lendacky@amd.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).