From: tomas.winkler@intel.com (Tomas Winkler)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 0/2] tpm: fix locality and power saving handling
Date: Sun, 28 Jan 2018 09:50:59 +0200 [thread overview]
Message-ID: <20180128075101.6883-1-tomas.winkler@intel.com> (raw)
Devices that support locality has failed to transmit due to
reserved order of locality request and cmdReady/goIdle handshake.
The cmdReady/goIdle should be performed on the requested locality.
The first patch corrects the locality and power-save order,
adds required polling for completion of goIdle and locality relinquish.
The second patch removes cmdRead/goIdle handshake from runtime_pm as it's
rather a part of TPM2 protocol then true device power management,
and on device it's no longer optional.
Tomas Winkler (2):
tpm: cmd_ready command can be issued only after granting locality
tpm: separate cmd_ready/go_idle from runtime_pm
drivers/char/tpm/tpm-interface.c | 21 ++++--
drivers/char/tpm/tpm_crb.c | 157 +++++++++++++++++++++++----------------
drivers/char/tpm/tpm_tis_core.c | 4 +-
include/linux/tpm.h | 4 +-
4 files changed, 115 insertions(+), 71 deletions(-)
--
2.14.3
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-01-28 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 7:50 Tomas Winkler [this message]
2018-01-28 7:51 ` [PATCH 1/2 v2] tpm: cmd_ready command can be issued only after granting locality Tomas Winkler
2018-01-28 20:15 ` Jason Gunthorpe
2018-01-28 21:17 ` Winkler, Tomas
2018-01-29 17:57 ` Jason Gunthorpe
2018-01-29 19:40 ` Winkler, Tomas
2018-02-06 20:02 ` Jarkko Sakkinen
2018-02-06 21:26 ` Winkler, Tomas
2018-02-08 12:44 ` Jarkko Sakkinen
2018-02-08 12:46 ` Winkler, Tomas
2018-01-28 7:51 ` [PATCH 2/2 v2] tpm: separate cmd_ready/go_idle from runtime_pm Tomas Winkler
2018-02-06 20:04 ` 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=20180128075101.6883-1-tomas.winkler@intel.com \
--to=tomas.winkler@intel.com \
--cc=linux-security-module@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).