All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Bernacki <bernacki@chromium.org>
To: jsd@semihalf.com
Cc: apronin@google.com, arnd@arndb.de, gregkh@linuxfoundation.org,
	jarkko@kernel.org, jgg@ziepe.ca, linux-integrity@vger.kernel.org,
	mw@semihalf.com, peterhuewe@gmx.de, rrangel@chromium.org,
	timvp@google.com, Grzegorz Bernacki <bernacki@chromium.org>
Subject: [PATCH V3 0/2]  char: tpm: Adjust cr50_i2c locking mechanism
Date: Thu, 10 Oct 2024 09:15:57 +0000	[thread overview]
Message-ID: <20241010091559.30866-1-bernacki@google.com> (raw)
In-Reply-To: <20221101020352.939691-1-jsd@semihalf.com>

From: Grzegorz Bernacki <bernacki@chromium.org>

This patchset contains two patches from original patchset which have
not yet be merged. As per original description:

This patchset aims to add support for a platforms with cr50(tpm) i2c
chip shared across two CPUs. We need to provide a mechanism, which will
allow to synchronize accesses on a TPM-transaction boundaries.

These two patches are modifying cr50 to use generic callbacks for
locality management and then leverage this solution to apply i2c bus
locking on a TPM-operation level.

Changes from V1:
- add dev_err() and return instead of WARN_ONCE()
- correct returned value in tpm_cr50_i2c_probe() functions
- I did not address Tim's suggestion to return 0 instead of loc
in check and request locality, I would like to follow convention
from tpm_tis_core.c file 

Changes from V2:
- remove unnecesary locality checking

Jan Dabros (2):
  char: tpm: cr50: Use generic request/relinquish locality ops
  char: tpm: cr50: Move i2c locking to request/relinquish locality ops

 drivers/char/tpm/tpm_tis_i2c_cr50.c | 114 ++++++++++++++++------------
 1 file changed, 66 insertions(+), 48 deletions(-)

-- 
2.47.0.rc0.187.ge670bccf7e-goog


  parent reply	other threads:[~2024-10-10  9:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  2:03 [PATCH 0/3] char: tpm: Adjust cr50_i2c locking mechanism Jan Dabros
2022-11-01  2:03 ` [PATCH 1/3] char: tpm: Protect tpm_pm_suspend with locks Jan Dabros
2022-11-01 15:53   ` Tim Van Patten
2022-11-02 21:28     ` Jan Dąbroś
2022-11-03 22:36       ` Tim Van Patten
2022-11-01  2:03 ` [PATCH 2/3] char: tpm: cr50: Use generic request/relinquish locality ops Jan Dabros
2022-11-01 16:04   ` Tim Van Patten
2022-11-02 21:42     ` Jan Dąbroś
2024-09-30 11:52     ` bernacki
2024-10-07 23:37       ` Jarkko Sakkinen
2022-11-01  2:03 ` [PATCH 3/3] char: tpm: cr50: Move i2c locking to " Jan Dabros
2024-10-09  9:42 ` [PATCH V2 0/2] char: tpm: Adjust cr50_i2c locking mechanism Grzegorz Bernacki
2024-10-09  9:42   ` [PATCH V2 1/2] char: tpm: cr50: Use generic request/relinquish locality ops Grzegorz Bernacki
2024-10-09 16:06     ` Jarkko Sakkinen
2024-10-09  9:42   ` [PATCH V2 2/2] char: tpm: cr50: Move i2c locking to " Grzegorz Bernacki
2024-10-09 16:07     ` Jarkko Sakkinen
2024-10-10  9:15 ` Grzegorz Bernacki [this message]
2024-10-10  9:15   ` [PATCH V3 1/2] char: tpm: cr50: Use generic " Grzegorz Bernacki
2024-10-10  9:15   ` [PATCH V3 2/2] char: tpm: cr50: Move i2c locking to " Grzegorz Bernacki
2024-10-28  9:09   ` [PATCH V3 0/2] char: tpm: Adjust cr50_i2c locking mechanism Grzegorz Bernacki
2024-10-28 12:16     ` 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=20241010091559.30866-1-bernacki@google.com \
    --to=bernacki@chromium.org \
    --cc=apronin@google.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko@kernel.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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.