linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Christian Bundy <christianbundy@fraction.io>,
	linux-integrity@vger.kernel.org
Subject: Re: PROBLEM: TPM bug causes suspend to turn off device
Date: Tue, 12 Nov 2019 21:43:08 +0200	[thread overview]
Message-ID: <20191112194249.GA8240@linux.intel.com> (raw)
In-Reply-To: <20191110072611.2k6tjt4geiq2rqol@cantor>

On Sun, Nov 10, 2019 at 12:26:11AM -0700, Jerry Snitselaar wrote:
> Jarkko, should there be tpm_chip_start/tpm_chip_stop calls around
> the tpm1_getcap calls in tpm1_get_timeouts?

Lookup tpm_chip_register().

/Jarkko

      parent reply	other threads:[~2019-11-12 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 19:13 PROBLEM: TPM bug causes suspend to turn off device Christian Bundy
2019-11-10  7:26 ` Jerry Snitselaar
2019-11-11 21:57   ` Jerry Snitselaar
2019-11-11 22:44     ` Christian Bundy
2019-11-12 19:43   ` 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=20191112194249.GA8240@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=christianbundy@fraction.io \
    --cc=jsnitsel@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    /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).