From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>, <linux-integrity@vger.kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Daniel P . Smith" <dpsmith@apertussolutions.com>,
"Lino Sanfilippo" <l.sanfilippo@kunbus.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Peter Huewe" <peterhuewe@gmx.de>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
"Alexander Steffen" <Alexander.Steffen@infineon.com>,
<keyrings@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: [PATCH v3] Documentation: tpm_tis
Date: Thu, 21 Mar 2024 19:01:09 +0200 [thread overview]
Message-ID: <CZZL841RSX3V.3SZOJNMC136O9@kernel.org> (raw)
In-Reply-To: <CZZL2SXZSRV0.2MGG3O8JXBFC5@kernel.org>
On Thu Mar 21, 2024 at 6:54 PM EET, Jarkko Sakkinen wrote:
> On Thu Mar 21, 2024 at 6:43 PM EET, Jarkko Sakkinen wrote:
> > Based recent discussions on LKML, provide preliminary bits of tpm_tis_core
> > dependent drivers. Includes only bare essentials but can be extended later
> > on case by case. This way some people may even want to read it later on.
>
> $ pdftotext PC-Client-Specific-Platform-TPM-Profile-for-TPM-2p0-v1p05p_r14_pub.pdf
> $ grep -ci 'FIFO interface' PC-Client-Specific-Platform-TPM-Profile-for-TPM-2p0-v1p05p_r14_pub.txt
> 55
>
> $ grep -ci 'TIS interface' PC-Client-Specific-Platform-TPM-Profile-for-TPM-2p0-v1p05p_r14_pub.txt
> 2
>
> 55 > 2 so that pretty much nails this terminology.
To add, this documentation *clears* the confusion in "FIFO vs TIS" by
documenting where TIS comes from (i.e. from the original TPM Interface
Spefication).
If you read the current standards you bump quite often (55 times in the
current spec) to FIFO interface, so it is good to clarify their relation
in the kernel documentation.
BR, Jarkko
prev parent reply other threads:[~2024-03-21 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:43 [PATCH v3] Documentation: tpm_tis Jarkko Sakkinen
2024-03-21 16:54 ` Jarkko Sakkinen
2024-03-21 17:01 ` 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=CZZL841RSX3V.3SZOJNMC136O9@kernel.org \
--to=jarkko@kernel.org \
--cc=Alexander.Steffen@infineon.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=corbet@lwn.net \
--cc=dpsmith@apertussolutions.com \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rdunlap@infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).