linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Peter Huewe <peterhuewe@gmx.de>,
	Ashley Lai <ashley@ashleylai.com>,
	Marcel Selhorst <tpmdd@selhorst.net>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	josh.triplett@intel.com, christophe.ricard@gmail.com,
	jason.gunthorpe@obsidianresearch.com
Subject: Re: [PATCH v5 0/7] TPM 2.0 support
Date: Sat, 1 Nov 2014 11:33:43 +0200	[thread overview]
Message-ID: <20141101093343.GA28272@intel.com> (raw)
In-Reply-To: <1414832495-23609-1-git-send-email-jarkko.sakkinen@linux.intel.com>

I pushed couples of fixed in addition to these changes to:

https://github.com/jsakkine/linux-tpm2/tree/tpm2-v5

There was problem running self-test because the FIFO module that I have
seems to give me TPM2_RC_TESTING when I try to start the self-test.

Additionally. I was able to test force parameter for tpm_tis. Resources
are cleaned up properly at least for TPM2 devices.

/Jarkko

On Sat, Nov 01, 2014 at 11:01:28AM +0200, Jarkko Sakkinen wrote:
> This patch set enables TPM2 protocol and provides drivers for FIFO and
> CRB interfaces.
> 
> Major changes since v1:
> 
> - Improved struct tpm_chip life-cycle by taking advantage of devres
>   API.
> - Refined sysfs attributes as simple key-values thereby not repeating
>   mistakes in TPM1 sysfs attributes.
> - Documented functions in tpm-chip.c and tpm2-cmd.c.
> - Documented sysfs attributes.
> 
> Major changes since v2:
> 
> - Lots of fixes in calling order in device drivers (thanks to Jason
>   Gunthorpe for pointing these out!).
> - Attach sysfs attributes to the misc device because it represents
>   TPM device to the user space.
> 
> Major changes since v3:
> 
> - Disable sysfs attibutes for TPM 2.0 for until we can sort out the 
>   best approach for them.
> - Fixed all the style issues found with checkpatch.pl.
> 
> Major changes since v4:
> 
> - missing EXPORT_SYMBOL_GPL()
> - own class for TPM devices used for TPM 2.0 devices and onwards.
> 
> Jarkko Sakkinen (6):
>   tpm: merge duplicate transmit_cmd() functions
>   tpm: two-phase chip management functions
>   tpm: fix multiple race conditions in tpm_ppi.c
>   tpm: TPM 2.0 baseline support
>   tpm: TPM 2.0 CRB Interface
>   tpm: create TPM 2.0 devices using own device class
> 
> Will Arthur (1):
>   tpm: TPM 2.0 FIFO Interface
> 
>  drivers/char/tpm/Kconfig            |   9 +
>  drivers/char/tpm/Makefile           |   3 +-
>  drivers/char/tpm/tpm-chip.c         | 209 +++++++++++++
>  drivers/char/tpm/tpm-dev.c          |  77 ++++-
>  drivers/char/tpm/tpm-interface.c    | 256 +++++-----------
>  drivers/char/tpm/tpm-sysfs.c        |  29 +-
>  drivers/char/tpm/tpm.h              | 113 ++++++-
>  drivers/char/tpm/tpm2-cmd.c         | 566 ++++++++++++++++++++++++++++++++++++
>  drivers/char/tpm/tpm_atmel.c        |  26 +-
>  drivers/char/tpm/tpm_crb.c          | 334 +++++++++++++++++++++
>  drivers/char/tpm/tpm_i2c_atmel.c    |  49 ++--
>  drivers/char/tpm/tpm_i2c_infineon.c |  43 +--
>  drivers/char/tpm/tpm_i2c_nuvoton.c  |  66 ++---
>  drivers/char/tpm/tpm_i2c_stm_st33.c |  44 ++-
>  drivers/char/tpm/tpm_ibmvtpm.c      |  17 +-
>  drivers/char/tpm/tpm_infineon.c     |  51 ++--
>  drivers/char/tpm/tpm_nsc.c          |  34 ++-
>  drivers/char/tpm/tpm_ppi.c          | 136 +++++----
>  drivers/char/tpm/tpm_tis.c          | 177 ++++++-----
>  drivers/char/tpm/xen-tpmfront.c     |  14 +-
>  20 files changed, 1711 insertions(+), 542 deletions(-)
>  create mode 100644 drivers/char/tpm/tpm-chip.c
>  create mode 100644 drivers/char/tpm/tpm2-cmd.c
>  create mode 100644 drivers/char/tpm/tpm_crb.c
> 
> -- 
> 2.1.0
> 

      parent reply	other threads:[~2014-11-01  9:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01  9:01 [PATCH v5 0/7] TPM 2.0 support Jarkko Sakkinen
2014-11-01  9:01 ` [PATCH v5 1/7] tpm: merge duplicate transmit_cmd() functions Jarkko Sakkinen
2014-11-01  9:01 ` [PATCH v5 2/7] tpm: two-phase chip management functions Jarkko Sakkinen
2014-11-01  9:01 ` [PATCH v5 3/7] tpm: fix multiple race conditions in tpm_ppi.c Jarkko Sakkinen
2014-11-01  9:01 ` [PATCH v5 4/7] tpm: TPM 2.0 baseline support Jarkko Sakkinen
2014-11-01  9:01 ` [PATCH v5 5/7] tpm: TPM 2.0 CRB Interface Jarkko Sakkinen
2014-11-01  9:01 ` [PATCH v5 6/7] tpm: TPM 2.0 FIFO Interface Jarkko Sakkinen
2014-11-01  9:01 ` [PATCH v5 7/7] tpm: create TPM 2.0 devices using own device class Jarkko Sakkinen
2014-11-02 21:33   ` Jason Gunthorpe
2014-11-03  5:41     ` Jarkko Sakkinen
2014-11-03 21:38       ` Jason Gunthorpe
2014-11-04 11:47         ` Jarkko Sakkinen
2014-11-04 12:05           ` Jarkko Sakkinen
2014-11-04 18:14           ` Jason Gunthorpe
2014-11-04 20:38             ` Jarkko Sakkinen
2014-11-04 20:49               ` Jason Gunthorpe
2014-11-04 23:00                 ` Jarkko Sakkinen
2014-11-05  7:40             ` Jarkko Sakkinen
2014-11-05 17:48               ` Jason Gunthorpe
2014-11-06  8:58                 ` Jarkko Sakkinen
2014-11-01  9:33 ` Jarkko Sakkinen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141101093343.GA28272@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=ashley@ashleylai.com \
    --cc=christophe.ricard@gmail.com \
    --cc=jason.gunthorpe@obsidianresearch.com \
    --cc=josh.triplett@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=tpmdd@selhorst.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).