From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: andrew.zamansky@nuvoton.com, tpmdd-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v2] tpm: Factor out common startup code
Date: Thu, 19 May 2016 12:07:14 +0300 [thread overview]
Message-ID: <20160519090714.GA12092@intel.com> (raw)
In-Reply-To: <20160518171320.GA15170@obsidianresearch.com>
On Wed, May 18, 2016 at 11:13:20AM -0600, Jason Gunthorpe wrote:
> On Wed, May 18, 2016 at 12:59:24PM +0300, Jarkko Sakkinen wrote:
> > On Tue, May 17, 2016 at 10:53:04AM -0600, Jason Gunthorpe wrote:
> > > On Tue, May 17, 2016 at 07:15:57AM +0300, Jarkko Sakkinen wrote:
> > > > On Mon, May 16, 2016 at 12:25:47PM -0600, Jason Gunthorpe wrote:
> > > > > Provide some flags in tpm_class_ops to allow drivers to opt-in to the
> > > > > common startup sequence. This is the sequence used by tpm_tis and
> > > > > tpm_crb.
> > > > >
> > > > > All drivers should set this flag.
> > > >
> > > > The commit message should be a much much more verbose I cannot include
> > > > this without a better explanation. Please update this for the next
> > > > revision.
> > >
> > > What more description do you want to see?
> >
> > It is lacking a lot of relevant information:
> >
> > * It should explain what you mean by startup sequence".
> > * It should describe the constant TPM_OPS_AUTO_STARTUP
> > * It should explain what drivers are doing at the moment (before
> > this feature).
> > * It should explain what is the benefit for different HW drivers
> > after applying this patch.
> > * It should explain why you call the executed sequence "automatic"
> > and also use the word "standard". Yeah, I didn't understand this,
> > this not me being picky. Maybe it should be DEFAULT_STARTUP??
>
> Well, use something like this then. You can edit descriptions to your
> liking when you apply the patch, FWIW.
>
> tpm: Factor out common startup code
>
> The TCG standard startup sequence (get timeouts, tpm startup, etc) for
> TPM and TPM2 chips is being open coded in many drivers, move it into
> the core code.
>
> tpm_tis and tpm_crb are used as the basis for the core code
> implementation and the easy drivers are converted. In the process
> several small drivers bugs relating to error handling this flow
> are fixed.
>
> For now the flag TPM_OPS_AUTO_STARTUP is optional to allow a staged
> driver roll out, but ultimately all drivers should use this flow and
> the flag removed. Some drivers still do not implement the startup
> sequence at all and will need to be tested with it enabled.
This is so much better! Thank you.
I can always edit a description but I do not want completely rewrite
them :)
/Jarkko
next prev parent reply other threads:[~2016-05-19 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 18:25 [PATCH v2] tpm: Factor out common startup code Jason Gunthorpe
2016-05-17 4:15 ` Jarkko Sakkinen
2016-05-17 16:53 ` Jason Gunthorpe
2016-05-18 9:59 ` Jarkko Sakkinen
2016-05-18 17:13 ` Jason Gunthorpe
2016-05-19 9:07 ` Jarkko Sakkinen [this message]
2016-05-26 12:23 ` Jarkko Sakkinen
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=20160519090714.GA12092@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=andrew.zamansky@nuvoton.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.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