From: Jarkko Sakkinen <jarkko@kernel.org>
To: Jan Dabros <jsd@semihalf.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
gregkh@linuxfoundation.org, arnd@arndb.de, rrangel@chromium.org,
timvp@google.com, apronin@google.com, mw@semihalf.com,
upstream@semihalf.com
Subject: Re: [PATCH v2 3/3] char: tpm: cr50: Move i2c locking to request/relinquish locality ops
Date: Mon, 7 Nov 2022 11:22:37 +0200 [thread overview]
Message-ID: <Y2jOXcsXCGyYtCR9@kernel.org> (raw)
In-Reply-To: <20221103145450.1409273-4-jsd@semihalf.com>
On Thu, Nov 03, 2022 at 03:54:50PM +0100, Jan Dabros wrote:
> Move i2c locking primitives to request_locality and relinquish_locality
> callbacks, what effectively blocks TPM bus for the whole duration of
> logical TPM operation.
>
> With this in place, cr50-equipped TPM may be shared with external CPUs -
> assuming that underneath i2c controller driver is aware of this setup
> (see i2c-designware-amdpsp as an example).
Nit: s/CPUs/peripherals/ ? I'm not sure why you want to emphasize external
chips having CPU.
>
> Signed-off-by: Jan Dabros <jsd@semihalf.com>
> ---
> drivers/char/tpm/tpm_tis_i2c_cr50.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/char/tpm/tpm_tis_i2c_cr50.c b/drivers/char/tpm/tpm_tis_i2c_cr50.c
> index 517d8410d7da0..f8a67fc2382cc 100644
> --- a/drivers/char/tpm/tpm_tis_i2c_cr50.c
> +++ b/drivers/char/tpm/tpm_tis_i2c_cr50.c
> @@ -202,8 +202,6 @@ static int tpm_cr50_i2c_read(struct tpm_chip *chip, u8 addr, u8 *buffer, size_t
> };
> int rc;
>
> - i2c_lock_bus(client->adapter, I2C_LOCK_SEGMENT);
> -
> /* Prepare for completion interrupt */
> tpm_cr50_i2c_enable_tpm_irq(chip);
>
> @@ -222,7 +220,6 @@ static int tpm_cr50_i2c_read(struct tpm_chip *chip, u8 addr, u8 *buffer, size_t
>
> out:
> tpm_cr50_i2c_disable_tpm_irq(chip);
> - i2c_unlock_bus(client->adapter, I2C_LOCK_SEGMENT);
>
> if (rc < 0)
> return rc;
> @@ -264,8 +261,6 @@ static int tpm_cr50_i2c_write(struct tpm_chip *chip, u8 addr, u8 *buffer,
> priv->buf[0] = addr;
> memcpy(priv->buf + 1, buffer, len);
>
> - i2c_lock_bus(client->adapter, I2C_LOCK_SEGMENT);
> -
> /* Prepare for completion interrupt */
> tpm_cr50_i2c_enable_tpm_irq(chip);
>
> @@ -279,7 +274,6 @@ static int tpm_cr50_i2c_write(struct tpm_chip *chip, u8 addr, u8 *buffer,
>
> out:
> tpm_cr50_i2c_disable_tpm_irq(chip);
> - i2c_unlock_bus(client->adapter, I2C_LOCK_SEGMENT);
>
> if (rc < 0)
> return rc;
> @@ -323,6 +317,7 @@ static int tpm_cr50_check_locality(struct tpm_chip *chip, int loc)
> */
> static int tpm_cr50_release_locality(struct tpm_chip *chip, int loc)
> {
> + struct i2c_client *client = to_i2c_client(chip->dev.parent);
> u8 mask = TPM_ACCESS_VALID | TPM_ACCESS_REQUEST_PENDING;
> u8 addr = TPM_I2C_ACCESS(loc);
> u8 buf;
> @@ -330,13 +325,15 @@ static int tpm_cr50_release_locality(struct tpm_chip *chip, int loc)
>
> rc = tpm_cr50_i2c_read(chip, addr, &buf, sizeof(buf));
> if (rc < 0)
> - return rc;
> + goto unlock_out;
>
> if ((buf & mask) == mask) {
> buf = TPM_ACCESS_ACTIVE_LOCALITY;
> rc = tpm_cr50_i2c_write(chip, addr, &buf, sizeof(buf));
> }
>
> +unlock_out:
> + i2c_unlock_bus(client->adapter, I2C_LOCK_SEGMENT);
> return rc;
> }
>
> @@ -351,16 +348,19 @@ static int tpm_cr50_release_locality(struct tpm_chip *chip, int loc)
> */
> static int tpm_cr50_request_locality(struct tpm_chip *chip, int loc)
> {
> + struct i2c_client *client = to_i2c_client(chip->dev.parent);
> u8 buf = TPM_ACCESS_REQUEST_USE;
> unsigned long stop;
> int rc;
>
> + i2c_lock_bus(client->adapter, I2C_LOCK_SEGMENT);
> +
> if (!tpm_cr50_check_locality(chip, loc))
> return loc;
>
> rc = tpm_cr50_i2c_write(chip, TPM_I2C_ACCESS(loc), &buf, sizeof(buf));
> if (rc < 0)
> - return rc;
> + goto unlock_out;
>
> stop = jiffies + chip->timeout_a;
> do {
> @@ -370,7 +370,11 @@ static int tpm_cr50_request_locality(struct tpm_chip *chip, int loc)
> msleep(TPM_CR50_TIMEOUT_SHORT_MS);
> } while (time_before(jiffies, stop));
>
> - return -ETIMEDOUT;
> + rc = -ETIMEDOUT;
> +
> +unlock_out:
> + i2c_unlock_bus(client->adapter, I2C_LOCK_SEGMENT);
> + return rc;
> }
>
> /**
> --
> 2.38.1.273.g43a17bfeac-goog
>
BR, Jarkko
next prev parent reply other threads:[~2022-11-07 9:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 14:54 [PATCH v2 0/3] char: tpm: Adjust cr50_i2c locking mechanism Jan Dabros
2022-11-03 14:54 ` [PATCH v2 1/3] char: tpm: Protect tpm_pm_suspend with locks Jan Dabros
2022-11-06 19:48 ` Jarkko Sakkinen
2022-11-07 8:45 ` Jan Dąbroś
2022-11-07 16:35 ` Jarkko Sakkinen
2022-11-28 17:04 ` Jason A. Donenfeld
2022-11-28 17:07 ` Jason A. Donenfeld
2022-11-28 19:46 ` Vlastimil Babka
2022-11-28 19:55 ` Jason A. Donenfeld
2022-11-28 17:11 ` Vlastimil Babka
2022-11-03 14:54 ` [PATCH v2 2/3] char: tpm: cr50: Use generic request/relinquish locality ops Jan Dabros
2022-11-07 9:20 ` Jarkko Sakkinen
2022-11-07 9:41 ` Jan Dąbroś
2022-11-18 14:09 ` Guenter Roeck
2022-11-03 14:54 ` [PATCH v2 3/3] char: tpm: cr50: Move i2c locking to " Jan Dabros
2022-11-07 9:22 ` Jarkko Sakkinen [this message]
2022-11-07 9:47 ` Jan Dąbroś
2022-11-07 16:35 ` 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=Y2jOXcsXCGyYtCR9@kernel.org \
--to=jarkko@kernel.org \
--cc=apronin@google.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=jsd@semihalf.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=peterhuewe@gmx.de \
--cc=rrangel@chromium.org \
--cc=timvp@google.com \
--cc=upstream@semihalf.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).