mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alexander.Steffen@infineon.com
Cc: chiu@endlessm.com, peterhuewe@gmx.de,
	jarkko.sakkinen@linux.intel.com, linux-integrity@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux@endlessm.com
Subject: Re: TPM driver breaks S3 suspend
Date: Thu, 21 Dec 2017 09:17:28 -0700	[thread overview]
Message-ID: <20171221161728.GB20015@ziepe.ca> (raw)
In-Reply-To: <5dbce6c25e7e499aaac05269ba3c0f73@infineon.com>

On Thu, Dec 21, 2017 at 10:19:09AM +0000, Alexander.Steffen@infineon.com wrote:

> The correct solution should be something like tpm2_auto_startup
> (execute selftests, if they fail because of the missing startup
> command, execute that and retry the selftests). Interestingly,
> tpm1_auto_startup (same purpose as tpm2_auto_startup, but for TPM
> 1.2 instead) does not use the same sequence, the startup-retry part
> is missing. Is there any reason this is done differently for TPM
> 1.2?

No TPM 1.2 has needed the retry loop so far.. don't see any problem
with adding it if the spec supports it.

Jason

  reply	other threads:[~2017-12-21 16:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21  8:04 Chris Chiu
2017-12-21  9:22 ` Paul Menzel
2017-12-21  9:43   ` Chris Chiu
2017-12-24 20:35     ` Jarkko Sakkinen
2017-12-21 10:19 ` Alexander.Steffen
2017-12-21 16:17   ` Jason Gunthorpe [this message]
2017-12-22  2:05   ` Chris Chiu
2017-12-22 13:34     ` Alexander.Steffen
2017-12-24 20:37   ` Jarkko Sakkinen
2017-12-24 20:33 ` Jarkko Sakkinen
2017-12-25  2:43   ` Chris Chiu
2018-01-02 14:43     ` Jarkko Sakkinen
2018-03-15 10:11       ` Daniel Drake
2018-03-16 13:44         ` 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=20171221161728.GB20015@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=Alexander.Steffen@infineon.com \
    --cc=chiu@endlessm.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=peterhuewe@gmx.de \
    /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

all inboxes | Powered by JetHome®