Linux-Integrity Archive mirror
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
	"Daniel P. Smith" <dpsmith@apertussolutions.com>,
	<linux-integrity@vger.kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
	"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>,
	"Richard Cochran" <richardcochran@gmail.com>,
	"open list:PTP HARDWARE CLOCK SUPPORT:Keyword:(?:b|_)ptp(?:b|_)"
	<netdev@vger.kernel.org>
Subject: Re: [PATCH v4] Documentation: tpm_tis
Date: Sun, 24 Mar 2024 04:14:36 +0200	[thread overview]
Message-ID: <D01M8YKG5ZG0.287OTMCUU2KP5@kernel.org> (raw)
In-Reply-To: <D01CLI2TC5SZ.1A48PDHM5F3UA@kernel.org>

On Sat Mar 23, 2024 at 8:40 PM EET, Jarkko Sakkinen wrote:
> > Would it be worth clarifying here that one of those interfaces is 
> > defined in the Mobile TPM specification, which also refers to its 
> > interface as the CRB interface. In the past, this has caused great 
> > confusion when working with individuals from the embedded community, 
> > e.g., Arm. The Mobile TPM CRB interface, which can also be found being 
> > used by some generations of AMD fTPM, is a doorbell style interface 
> > using general-purpose memory. I would also point out that the Mobile TPM 
> > CRB interface does not provide for the concept of localities.
>
> I don't necessarily disagree but it is out of scope for this. I'm not
> sure tho why "mobile" CRB would ever need that sort of separate
> dicussion.
>
> Some CRB implementations have localities some don't, and also fTPM
> implementations on x86 vary, no need to state that separately for
> mobile.

I.e. the variance exist but it is not "mobile" specific.

E.g. when I developed tpm_crb in 2014 at that time Intel PTT only
had a single locality (AFAIK later multiple localities were added
to support TXT).

In all cases this tpm_crb discussion is not really part of tpm_tis
discussion.

BR, Jarkko

      reply	other threads:[~2024-03-24  2:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 12:35 [PATCH v4] Documentation: tpm_tis Jarkko Sakkinen
2024-03-22 22:52 ` Jakub Kicinski
2024-03-23 18:25   ` Jarkko Sakkinen
2024-03-23  0:39 ` Daniel P. Smith
2024-03-23 18:40   ` Jarkko Sakkinen
2024-03-24  2:14     ` 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=D01M8YKG5ZG0.287OTMCUU2KP5@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=netdev@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=rdunlap@infradead.org \
    --cc=richardcochran@gmail.com \
    /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).