From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-integrity@vger.kernel.org, James Morris <jmorris@namei.org>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
stable <stable@vger.kernel.org>
Subject: Re: [GIT PULL] tpmdd updates for Linux v5.4
Date: Fri, 6 Dec 2019 23:18:34 +0200 [thread overview]
Message-ID: <20191206211834.GD9971@linux.intel.com> (raw)
In-Reply-To: <20191130001253.rtovohtfbg25uifm@cantor>
On Fri, Nov 29, 2019 at 05:12:53PM -0700, Jerry Snitselaar wrote:
> On Sat Nov 30 19, Jarkko Sakkinen wrote:
> > On Wed, Nov 27, 2019 at 06:20:55PM -0700, Jerry Snitselaar wrote:
> > > There also was that other issue reported on the list about
> > > tpm_tis_core_init failing when calling tpm_get_timeouts due to the
> > > power gating changes.
> >
> > Please add a (lore.ko) link for reference to this thread.
> >
> > /Jarkko
> >
>
> https://lore.kernel.org/linux-integrity/a60dadce-3650-44ce-8785-2f737ab9b993@www.fastmail.com/
tpm_chip_stop() probably causes the issue. That is why tpm2_probe()
works and failure happens after that.
tpm_chip_stop() should be called once at the end of the function.
/Jarkko
next prev parent reply other threads:[~2019-12-06 21:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 14:31 [GIT PULL] tpmdd updates for Linux v5.4 Jarkko Sakkinen
2019-09-16 21:35 ` pr-tracker-bot
2019-11-21 4:48 ` Dan Williams
2019-11-22 16:18 ` Jerry Snitselaar
2019-11-29 21:04 ` Jarkko Sakkinen
2019-11-29 23:22 ` Jerry Snitselaar
2019-11-29 23:32 ` Jerry Snitselaar
2019-12-06 20:51 ` Jarkko Sakkinen
2019-12-06 20:50 ` Jarkko Sakkinen
2019-11-27 20:58 ` Jarkko Sakkinen
2019-11-27 20:59 ` Jarkko Sakkinen
2019-11-28 1:20 ` Jerry Snitselaar
2019-11-29 23:53 ` Jarkko Sakkinen
2019-11-30 0:12 ` Jerry Snitselaar
2019-12-06 21:18 ` Jarkko Sakkinen [this message]
2019-12-06 23:02 ` Jerry Snitselaar
2019-12-09 20:17 ` Jarkko Sakkinen
2019-11-27 21:10 ` Dan Williams
2019-11-29 23:25 ` 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=20191206211834.GD9971@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.