From: Jarkko Sakkinen <jarkko@kernel.org>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>,
linux-integrity@vger.kernel.org
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org,
Alexander Steffen <Alexander.Steffen@infineon.com>,
Michael Haener <michael.haener@siemens.com>
Subject: Re: [PATCH 1/2] tpm: tis_i2c: Limit read bursts to I2C_SMBUS_BLOCK_MAX (32) bytes
Date: Wed, 24 May 2023 19:03:43 +0300 [thread overview]
Message-ID: <d0b56100e7a8cdea42972637d2c32fce367a8286.camel@kernel.org> (raw)
In-Reply-To: <20230524154040.1204030-1-alexander.sverdlin@siemens.com>
On Wed, 2023-05-24 at 17:40 +0200, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> Underlying I2C bus drivers not always support longer transfers and
> imx-lpi2c for instance doesn't. SLB 9673 offers 427-bytes packets.
>
> Visible symptoms are:
>
> tpm tpm0: Error left over data
> tpm tpm0: tpm_transmit: tpm_recv: error -5
> tpm_tis_i2c: probe of 1-002e failed with error -5
>
> Fixes: bbc23a07b072 ("tpm: Add tpm_tis_i2c backend for tpm_tis_core")
> Tested-by: Michael Haener <michael.haener@siemens.com>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
next prev parent reply other threads:[~2023-05-24 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 15:40 [PATCH 1/2] tpm: tis_i2c: Limit read bursts to I2C_SMBUS_BLOCK_MAX (32) bytes A. Sverdlin
2023-05-24 15:40 ` [PATCH 2/2] tpm: tis_i2c: Limit write " A. Sverdlin
2023-05-24 22:05 ` Jerry Snitselaar
2023-06-06 21:24 ` Jarkko Sakkinen
2023-05-24 16:03 ` Jarkko Sakkinen [this message]
2023-05-24 18:19 ` [PATCH 1/2] tpm: tis_i2c: Limit read " Jerry Snitselaar
2023-06-06 21:23 ` 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=d0b56100e7a8cdea42972637d2c32fce367a8286.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=Alexander.Steffen@infineon.com \
--cc=alexander.sverdlin@siemens.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.haener@siemens.com \
--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