From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Scot Doyle <lkml14@scotdoyle.com>,
peterhuewe@gmx.de, ashley@ashleylai.com,
christophe.ricard@gmail.com,
jason.gunthorpe@obsidianresearch.com, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
trousers-tech@lists.sourceforge.net
Subject: Re: [tpmdd-devel] [PATCH] tpm: fix suspend/resume paths for TPM 2.0
Date: Tue, 27 Jan 2015 10:03:08 -0700 [thread overview]
Message-ID: <20150127170308.GA10140@obsidianresearch.com> (raw)
In-Reply-To: <1422377842.2912.1.camel@linux.intel.com>
On Tue, Jan 27, 2015 at 06:57:22PM +0200, Jarkko Sakkinen wrote:
> > > + /* TPM 1.2 requires self-test on resume. */
> > > + if (!(chip->flags & TPM_CHIP_FLAG_TPM2)) {
> > > + ret = tpm_do_selftest(chip);
> > > + if (ret < 0)
> > > + return ret;
> >
> > Just to note, the return value from tpm_do_selftest() on TPM 1.2 chips was
> > previously ignored. Mine does return 0.
>
> Right. I can update the patch to ignore return value if the majority
> wants that.
What happens to the system when pnp_driver.resume() returns failure?
Should tpm ever report failure on resume to the rest of the kernel?
Shouldn't this stuff be in tpm_pm_resume common code anyhow?
Jason
next prev parent reply other threads:[~2015-01-27 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 11:02 [PATCH] tpm: fix suspend/resume paths for TPM 2.0 Jarkko Sakkinen
2015-01-27 16:52 ` [tpmdd-devel] " Scot Doyle
2015-01-27 16:57 ` Jarkko Sakkinen
2015-01-27 17:03 ` Jason Gunthorpe [this message]
2015-01-27 17:23 ` Jarkko Sakkinen
2015-01-27 17:33 ` 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=20150127170308.GA10140@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=ashley@ashleylai.com \
--cc=christophe.ricard@gmail.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jason.gunthorpe@obsidianresearch.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml14@scotdoyle.com \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=trousers-tech@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