Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1499028
| From | Jason Gunthorpe <jgunthorpe@obsidianresearch.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] char/tpm: Check return code of wait_for_tpm_stat |
| Date | 2016-10-11 19:20 +0200 |
| Message-ID | <sr8SB-12j-11@gated-at.bofh.it> (permalink) |
| References | <sr42B-6yT-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Oct 11, 2016 at 03:01:01PM +0300, Jarkko Sakkinen wrote: > From: Peter Huewe <peterhuewe@gmx.de> > > 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? Jason
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] char/tpm: Check return code of wait_for_tpm_stat Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> - 2016-10-11 14:10 +0200
Re: [PATCH] char/tpm: Check return code of wait_for_tpm_stat Jason Gunthorpe <jgunthorpe@obsidianresearch.com> - 2016-10-11 19:20 +0200
Re: [PATCH] char/tpm: Check return code of wait_for_tpm_stat Peter Huewe <peterhuewe@gmx.de> - 2016-10-11 20:30 +0200
Re: [PATCH] char/tpm: Check return code of wait_for_tpm_stat Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> - 2016-10-12 14:20 +0200
csiph-web