Re: [PATCH] char/tpm: Check return code of wait_for_tpm_stat
From: Jason Gunthorpe
Date: Tue Oct 11 2016 - 13:13:35 EST
On Tue, Oct 11, 2016 at 03:01:01PM +0300, Jarkko Sakkinen wrote:
> From: Peter Huewe <peterhuewe@xxxxxx>
> In some weird cases it might be possible that the TPM does not set
> STS.VALID within the given timeout time (or ever) but sets STS.EXPECT
> (STS=0x0C) In this case the driver gets stuck in the while loop of
> tpm_tis_send_data and loops endlessly.
Doesn't that exchange mean the TPM has lost synchronization with the
driver? Or maybe it crashed executing a command or something..
Please indicate what hardware is broken like this.. Or how did you get
it to do this?