Re: [PATCH v9 0/5] tpm: Command duration logging and chip-specific override
From: Jarkko Sakkinen
Date: Mon Jul 18 2016 - 14:08:08 EST
On Wed, Jul 13, 2016 at 09:19:31AM -0700, Ed Swierk wrote:
> v9: Include command duration in existing error messages rather than
> logging an extra debug message. Rebase onto Jarkko's tree.
> v8: Fix v7 goof-up in tpm_getcap().
> v7: Use tpm_getcap() instead of a redundant new function.
> v6: Split tpm_get_cap_prop() out of tpm_get_timeouts(); always return
> error on TPM command failure.
> v5: Use msecs_to_jiffies() instead of * HZ / 1000.
> v4: Rework tpm_get_timeouts() to allow overriding both timeouts and
> durations via a single callback.
> This series
> - improves TPM command error reporting
> - adds optional logging of TPM command durations
> - allows chip-specific override of command durations as well as protocol
> - overrides ST19NP18 TPM command duration to avoid lockups
For the next version please write something more readable. Describe the
motivation and solution in big picture, why and how. This list does no
good because it just mimics the list of patches.
> Ed Swierk (5):
> tpm_tis: Improve reporting of IO errors
> tpm: Add optional logging of TPM command durations
> tpm: Clean up reading of timeout and duration capabilities
> tpm: Allow TPM chip drivers to override reported command durations
> tpm_tis: Increase ST19NP18 TPM command duration to avoid chip lockup
> drivers/char/tpm/tpm-interface.c | 219 ++++++++++++++++++++-------------------
> drivers/char/tpm/tpm_tis_core.c | 46 ++++----
> include/linux/tpm.h | 3 +-
> 3 files changed, 136 insertions(+), 132 deletions(-)