From: Andrew Lunn <andrew@lunn.ch>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
apronin@google.com, tpmdd-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Bryan Freed <bfreed@chromium.org>
Subject: Re: [tpmdd-devel] [PATCH 1/2] tpm: Apply an adapterlimit for retransmission.
Date: Tue, 21 Feb 2017 17:29:48 +0100 [thread overview]
Message-ID: <20170221162948.GD25818@lunn.ch> (raw)
In-Reply-To: <20170221144500.502-1-enric.balletbo@collabora.com>
On Tue, Feb 21, 2017 at 03:44:59PM +0100, Enric Balletbo i Serra wrote:
> From: Bryan Freed <bfreed@chromium.org>
>
> When the I2C Infineon part is attached to an I2C adapter that imposes
> a size limitation, large requests will fail -EINVAL.
> Retry them with size backoff without re-issuing the 0x05 command
> as this appears to occasionally put the TPM in a bad state.
Hi Enric
Rather than trying small and smaller transfers, would it not be better
to get the i2c core to expose the quirk info about transfer limits?
Andrew
next prev parent reply other threads:[~2017-02-21 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 14:44 [PATCH 1/2] tpm: Apply an adapterlimit for retransmission Enric Balletbo i Serra
2017-02-21 14:45 ` [PATCH 2/2] tpm: Do not assume an i2c adapter preserves the msg len Enric Balletbo i Serra
2017-02-21 16:29 ` Andrew Lunn [this message]
2017-02-22 11:16 ` [tpmdd-devel] [PATCH 1/2] tpm: Apply an adapterlimit for retransmission Enric Balletbo i Serra
2017-02-22 14:01 ` Andrew Lunn
2017-02-27 18:48 ` Enric Balletbo Serra
[not found] ` <CAFqH_536FjjkWiUS_5PyDJHHgy6S8BvBzArAxSAg6H6oa214KA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-27 19:12 ` Wolfram Sang
2017-02-27 21:30 ` Enric Balletbo Serra
2017-03-02 13:15 ` Peter Huewe
2017-03-02 14:05 ` [tpmdd-devel] " Wolfram Sang
2017-03-02 14:10 ` Wolfram Sang
[not found] ` <20170221162948.GD25818-g2DYL2Zd6BY@public.gmane.org>
2017-02-22 12:39 ` Peter Huewe
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=20170221162948.GD25818@lunn.ch \
--to=andrew@lunn.ch \
--cc=apronin@google.com \
--cc=bfreed@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
/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).