From: Jarkko Sakkinen <jarkko@kernel.org>
To: Prachotan Bathi <prachotan.bathi@arm.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Stuart Yoder <stuart.yoder@arm.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/1] tpm_ffa_crb: handle tpm busy return code
Date: Tue, 10 Jun 2025 00:00:35 +0300 [thread overview]
Message-ID: <aEdLc_OpTNvsk5pl@kernel.org> (raw)
In-Reply-To: <20250609141600.3601340-1-prachotan.bathi@arm.com>
On Mon, Jun 09, 2025 at 09:15:59AM -0500, Prachotan Bathi wrote:
> Platforms supporting direct message request v2 can
> support SPs that support multiple services.
What is "direct message request v2"?
> If the TPM service is sharing the SP with another service,
> it could get an error code of BUSY if the other service is
> in process.
> We need a way for the driver to retry sending the message
> to the TPM service until it succeeds or we know that no forward progress
> can be made.
> This patch adds a parameterized variable (default 2000ms)
> that indicates the maximum time to keep retrying for.
>
> Prachotan Bathi (1):
> tpm_ffa_crb: handle tpm busy return code
>
> drivers/char/tpm/tpm_crb_ffa.c | 74 +++++++++++++++++++++++-----------
> 1 file changed, 50 insertions(+), 24 deletions(-)
>
> --
> 2.43.0
>
>
BR, Jarkko
next prev parent reply other threads:[~2025-06-09 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 14:15 [PATCH v1 0/1] tpm_ffa_crb: handle tpm busy return code Prachotan Bathi
2025-06-09 14:16 ` [PATCH v1 1/1] " Prachotan Bathi
2025-06-09 21:02 ` Jarkko Sakkinen
2025-06-09 21:00 ` Jarkko Sakkinen [this message]
2025-06-10 21:12 ` [PATCH v1 0/1] " Prachotan Bathi
2025-06-11 16:43 ` Jarkko Sakkinen
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=aEdLc_OpTNvsk5pl@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=prachotan.bathi@arm.com \
--cc=stuart.yoder@arm.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