summaryrefslogtreecommitdiff
path: root/drivers/char/tpm/tpm-dev.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-01-06 14:49:52 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2020-01-06 14:49:52 -0800
commit7ae564122f75337d84c41b3963a6e25e8665dfac (patch)
tree0375a8959662747d4854cef9f686a78a1cfcf19c /drivers/char/tpm/tpm-dev.h
parentbaf4dc829574ed9dd8ba33cda0536a50f28937de (diff)
parentaa4a63dd981682b1742baa01237036e48bc11923 (diff)
Merge tag 'tpmdd-next-20200106' of git://git.infradead.org/users/jjs/linux-tpmdd
Pull tpmd fixes from Jarkko Sakkinen: "There has been a bunch of reports (e.g. [*]) reporting that when commit 5b359c7c4372 ("tpm_tis_core: Turn on the TPM before probing IRQ's") and subsequent fixes are applied it causes boot freezes on some machines. Unfortunately hardware where this causes a failure is not widely available (only one I'm aware is Lenovo T490), which means we cannot predict yet how long it will take to properly fix tpm_tis interrupt probing. Thus, the least worst short term action is to revert the code to the state before this commit. In long term we need fix the tpm_tis probing code to work on machines that Stefan's patches were supposed to fix. With these patches reverted nothing fatal happens, TPM is fallbacked to be used in polling mode (which is not in the end too bad because there are no high throughput workloads for TPM). [*] https://bugzilla.kernel.org/show_bug.cgi?id=205935" * tag 'tpmdd-next-20200106' of git://git.infradead.org/users/jjs/linux-tpmdd: tpm: Revert "tpm_tis_core: Turn on the TPM before probing IRQ's" tpm: Revert "tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts" tpm: Revert "tpm_tis: reserve chip for duration of tpm_tis_core_init"
Diffstat (limited to 'drivers/char/tpm/tpm-dev.h')
0 files changed, 0 insertions, 0 deletions