From: Jarkko Sakkinen <jarkko@kernel.org>
To: Adrian Ratiu <adrian.ratiu@collabora.com>
Cc: linux-integrity@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org, kernel@collabora.com,
"dlaurie@chromium.org" <dlaurie@chromium.org>,
Helen Koike <helen.koike@collabora.com>,
Ezequiel Garcia <ezequiel@collabora.com>
Subject: Re: [PATCH v6] char: tpm: add i2c driver for cr50
Date: Fri, 11 Dec 2020 12:34:43 +0200 [thread overview]
Message-ID: <20201211103443.GA12091@kernel.org> (raw)
In-Reply-To: <87y2i7b186.fsf@collabora.com>
On Wed, Dec 09, 2020 at 02:41:45PM +0200, Adrian Ratiu wrote:
> On Tue, 08 Dec 2020, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > On Mon, Dec 07, 2020 at 04:20:16PM +0200, Adrian Ratiu wrote:
> > > From: "dlaurie@chromium.org" <dlaurie@chromium.org> Add TPM 2.0
> > > compatible I2C interface for chips with cr50 firmware. The firmware
> > > running on the currently supported H1 MCU requires a special driver
> > > to handle its specific protocol, and this makes it unsuitable to use
> > > tpm_tis_core_* and instead it must implement the underlying TPM
> > > protocol similar to the other I2C TPM drivers. - All 4 bytes of
> > > status register must be read/written at once. - FIFO and burst
> > > count is limited to 63 and must be drained by AP. - Provides an
> > > interrupt to indicate when read response data is ready and when the
> > > TPM is finished processing write data. This driver is based on the
> > > existing infineon I2C TPM driver, which most closely matches the
> > > cr50 i2c protocol behavior.
> >
> > Starts to look legit. Has anyone tested this?
>
> I tested on an x86_64 Chromebook EVE (aka Google Pixelbook) by chainloading
> in legacy mode and booting into a Yocto-based userspace (meta-chromebook)
> where I used tpm2-tools to communicate with the chip and also built and
> tested a ChromiumOS userspace in developer mode.
>
> I do not have access to other HW which has this chip, so it is about as much
> testing I can do to confirm the driver works on this HW.
>
> Adrian
So can you respond to this with tested-by. It's sufficient because
collateral effects of driver failing are insignificant for the kernel
as whole.
/Jarkko
next prev parent reply other threads:[~2020-12-11 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 14:20 [PATCH v6] char: tpm: add i2c driver for cr50 Adrian Ratiu
2020-12-08 17:39 ` Jarkko Sakkinen
2020-12-09 12:41 ` Adrian Ratiu
2020-12-11 10:34 ` Jarkko Sakkinen [this message]
2020-12-14 16:37 ` Adrian Ratiu
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=20201211103443.GA12091@kernel.org \
--to=jarkko@kernel.org \
--cc=adrian.ratiu@collabora.com \
--cc=dlaurie@chromium.org \
--cc=ezequiel@collabora.com \
--cc=helen.koike@collabora.com \
--cc=jgg@ziepe.ca \
--cc=kernel@collabora.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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).