From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stuart Yoder <stuart.yoder@arm.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
sudeep.holla@arm.com, rafael@kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/5] tpm_crb: clean-up and refactor check for idle support
Date: Thu, 20 Feb 2025 11:29:42 +0200 [thread overview]
Message-ID: <Z7b2BlllE6HVIZNN@kernel.org> (raw)
In-Reply-To: <20250219201014.174344-3-stuart.yoder@arm.com>
On Wed, Feb 19, 2025 at 02:10:11PM -0600, Stuart Yoder wrote:
> Refactor TPM idle check to tpm_crb_has_idle(), and reduce paraentheses
> usage in start method checks
>
> Signed-off-by: Stuart Yoder <stuart.yoder@arm.com>
> ---
> drivers/char/tpm/tpm_crb.c | 36 +++++++++++++++++++++---------------
> 1 file changed, 21 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c
> index ea085b14ab7c..31db879f1324 100644
> --- a/drivers/char/tpm/tpm_crb.c
> +++ b/drivers/char/tpm/tpm_crb.c
> @@ -115,6 +115,16 @@ struct tpm2_crb_pluton {
> u64 reply_addr;
> };
>
> +/*
> + * Returns true if the start method supports idle.
> + */
> +static inline bool tpm_crb_has_idle(u32 start_method)
> +{
> + return start_method == ACPI_TPM2_START_METHOD ||
> + start_method == ACPI_TPM2_COMMAND_BUFFER_WITH_START_METHOD ||
> + start_method == ACPI_TPM2_COMMAND_BUFFER_WITH_ARM_SMC;
> +}
> +
> static bool crb_wait_for_reg_32(u32 __iomem *reg, u32 mask, u32 value,
> unsigned long timeout)
> {
> @@ -173,9 +183,7 @@ static int __crb_go_idle(struct device *dev, struct crb_priv *priv)
> {
> int rc;
>
> - if ((priv->sm == ACPI_TPM2_START_METHOD) ||
> - (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_START_METHOD) ||
> - (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_ARM_SMC))
> + if (!tpm_crb_has_idle(priv->sm))
> return 0;
>
> iowrite32(CRB_CTRL_REQ_GO_IDLE, &priv->regs_t->ctrl_req);
> @@ -222,9 +230,7 @@ static int __crb_cmd_ready(struct device *dev, struct crb_priv *priv)
> {
> int rc;
>
> - if ((priv->sm == ACPI_TPM2_START_METHOD) ||
> - (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_START_METHOD) ||
> - (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_ARM_SMC))
> + if (!tpm_crb_has_idle(priv->sm))
> return 0;
>
> iowrite32(CRB_CTRL_REQ_CMD_READY, &priv->regs_t->ctrl_req);
> @@ -423,13 +429,13 @@ static int crb_send(struct tpm_chip *chip, u8 *buf, size_t len)
> * report only ACPI start but in practice seems to require both
> * CRB start, hence invoking CRB start method if hid == MSFT0101.
> */
> - if ((priv->sm == ACPI_TPM2_COMMAND_BUFFER) ||
> - (priv->sm == ACPI_TPM2_MEMORY_MAPPED) ||
> - (!strcmp(priv->hid, "MSFT0101")))
> + if (priv->sm == ACPI_TPM2_COMMAND_BUFFER ||
> + priv->sm == ACPI_TPM2_MEMORY_MAPPED ||
> + !strcmp(priv->hid, "MSFT0101"))
> iowrite32(CRB_START_INVOKE, &priv->regs_t->ctrl_start);
>
> - if ((priv->sm == ACPI_TPM2_START_METHOD) ||
> - (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_START_METHOD))
> + if (priv->sm == ACPI_TPM2_START_METHOD ||
> + priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_START_METHOD)
> rc = crb_do_acpi_start(chip);
>
> if (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_ARM_SMC) {
> @@ -449,8 +455,8 @@ static void crb_cancel(struct tpm_chip *chip)
>
> iowrite32(CRB_CANCEL_INVOKE, &priv->regs_t->ctrl_cancel);
>
> - if (((priv->sm == ACPI_TPM2_START_METHOD) ||
> - (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_START_METHOD)) &&
> + if ((priv->sm == ACPI_TPM2_START_METHOD ||
> + priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_START_METHOD) &&
> crb_do_acpi_start(chip))
> dev_err(&chip->dev, "ACPI Start failed\n");
> }
> @@ -609,8 +615,8 @@ static int crb_map_io(struct acpi_device *device, struct crb_priv *priv,
> * the control area, as one nice sane region except for some older
> * stuff that puts the control area outside the ACPI IO region.
> */
> - if ((priv->sm == ACPI_TPM2_COMMAND_BUFFER) ||
> - (priv->sm == ACPI_TPM2_MEMORY_MAPPED)) {
> + if (priv->sm == ACPI_TPM2_COMMAND_BUFFER ||
> + priv->sm == ACPI_TPM2_MEMORY_MAPPED) {
> if (iores &&
> buf->control_address == iores->start +
> sizeof(*priv->regs_h))
> --
> 2.34.1
>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
next prev parent reply other threads:[~2025-02-20 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 20:10 [PATCH v5 0/5] Add support for the TPM FF-A start method Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 1/5] tpm_crb: implement driver compliant to CRB over FF-A Stuart Yoder
2025-02-20 9:28 ` Jarkko Sakkinen
2025-02-20 9:31 ` Jarkko Sakkinen
2025-02-20 19:02 ` Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 2/5] tpm_crb: clean-up and refactor check for idle support Stuart Yoder
2025-02-20 9:29 ` Jarkko Sakkinen [this message]
2025-02-20 19:04 ` Stuart Yoder
2025-02-20 19:09 ` Paul Menzel
2025-02-20 21:36 ` Jarkko Sakkinen
2025-02-20 21:35 ` Jarkko Sakkinen
2025-02-19 20:10 ` [PATCH v5 3/5] ACPICA: add start method for Arm FF-A Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 4/5] tpm_crb: add support for the Arm FF-A start method Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 5/5] Documentation: tpm: add documentation for the CRB FF-A interface Stuart Yoder
2025-02-20 9:30 ` 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=Z7b2BlllE6HVIZNN@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rafael@kernel.org \
--cc=stuart.yoder@arm.com \
--cc=sudeep.holla@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;
as well as URLs for NNTP newsgroup(s).