From mboxrd@z Thu Jan  1 00:00:00 1970
From: Miquel Raynal <miquel.raynal@bootlin.com>
Date: Mon, 18 Jun 2018 10:04:59 +0200
Subject: [U-Boot] tpm TIS TPMv2.0
In-Reply-To: <CD66EE5B80A65C4A89E8DE986277AC94200D1B9D@depoiy0mx08mbx2.emea.avnet.com>
References: <CD66EE5B80A65C4A89E8DE986277AC94200D1B9D@depoiy0mx08mbx2.emea.avnet.com>
Message-ID: <20180618100500.41e32bc9@xps13>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: u-boot@lists.denx.de

Hi Martin,

On Fri, 15 Jun 2018 13:34:07 +0000, "Hecht, Martin (Avnet Silica)"
<Martin.Hecht@avnet.eu> wrote:

> Hi Miquel, Simon,
>=20
> Is there any specific reason why the new tpm2_tis_spi_xfer doesn't suppor=
t full duplex? It seems we did some work in parallel but you sent the patch=
es earlier. Is that codes tested against an existing TPM v2? I have a worki=
ng implementation what runs on SLB9670 including full duplex.

What do you mean exactly?

I don't think the TPM2 protocol makes real use of full-duplex unless
for the wait state between the host command and the actual xfer.

Regards,
Miqu=C3=A8l