linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: peterhuewe@gmx.de, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca,
	corbet@lwn.net, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-integrity@vger.kernel.org,
	linux-kernel@microsoft.com, thiruan@microsoft.com,
	bryankel@microsoft.com, tee-dev@lists.linaro.org,
	ilias.apalodimas@linaro.org, sumit.garg@linaro.org
Subject: Re: [PATCH v6 2/2] fTPM: add documentation for ftpm driver
Date: Tue, 25 Jun 2019 16:03:10 -0400	[thread overview]
Message-ID: <20190625200310.GC7898@sasha-vm> (raw)
In-Reply-To: <b1f27a59-6759-c325-8db5-b2b0f944420c@infradead.org>

On Tue, Jun 25, 2019 at 12:59:02PM -0700, Randy Dunlap wrote:
>On 6/25/19 12:52 PM, Sasha Levin wrote:
>> This patch adds basic documentation to describe the new fTPM driver.
>>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>>  Documentation/security/tpm/index.rst        |  1 +
>>  Documentation/security/tpm/tpm_ftpm_tee.rst | 31 +++++++++++++++++++++
>>  2 files changed, 32 insertions(+)
>>  create mode 100644 Documentation/security/tpm/tpm_ftpm_tee.rst
>>
>> diff --git a/Documentation/security/tpm/index.rst b/Documentation/security/tpm/index.rst
>> index af77a7bbb070..15783668644f 100644
>> --- a/Documentation/security/tpm/index.rst
>> +++ b/Documentation/security/tpm/index.rst
>> @@ -4,4 +4,5 @@ Trusted Platform Module documentation
>>
>>  .. toctree::
>>
>> +   tpm_ftpm_tee
>>     tpm_vtpm_proxy
>> diff --git a/Documentation/security/tpm/tpm_ftpm_tee.rst b/Documentation/security/tpm/tpm_ftpm_tee.rst
>> new file mode 100644
>> index 000000000000..29c2f8b5ed10
>> --- /dev/null
>> +++ b/Documentation/security/tpm/tpm_ftpm_tee.rst
>> @@ -0,0 +1,31 @@
>> +=============================================
>> +Firmware TPM Driver
>> +=============================================
>> +
>> +| Authors:
>> +| Thirupathaiah Annapureddy <thiruan@microsoft.com>
>> +| Sasha Levin <sashal@kernel.org>
>> +
>> +This document describes the firmware Trusted Platform Module (fTPM)
>> +device driver.
>> +
>> +Introduction
>> +============
>> +
>> +This driver is a shim for a firmware implemented in ARM's TrustZone
>
>                         for firmware
>
>> +environment. The driver allows programs to interact with the TPM in the same
>> +way the would interact with a hardware TPM.
>
>       they
>
>> +
>> +Design
>> +======
>> +
>> +The driver acts as a thin layer that passes commands to and from a TPM
>> +implemented in firmware. The driver itself doesn't contain much logic and is
>> +used more like a dumb pipe between firmware and kernel/userspace.
>> +
>> +The firmware itself is based on the following paper:
>> +https://www.microsoft.com/en-us/research/wp-content/uploads/2017/06/ftpm1.pdf
>> +
>> +When the driver is loaded it will expose ``/dev/tpmX`` character devices to
>> +userspace which will enable userspace to communicate with the firmware tpm
>
>                                                                          TPM
>
>> +through this device.
>>
>
>Oh, that's the same comments that I made on 2019-06-18:
>https://marc.info/?l=linux-integrity&m=156087157019368&w=2

Appologies Randy, I've missed it. I'll send a new ver in a moment.
Thanks!

--
Thanks,
Sasha

      reply	other threads:[~2019-06-25 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 19:52 [PATCH v6 0/2] fTPM: firmware TPM running in TEE Sasha Levin
2019-06-25 19:52 ` [PATCH v6 1/2] " Sasha Levin
2019-06-25 20:01   ` Randy Dunlap
2019-06-25 19:52 ` [PATCH v6 2/2] fTPM: add documentation for ftpm driver Sasha Levin
2019-06-25 19:59   ` Randy Dunlap
2019-06-25 20:03     ` Sasha Levin [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=20190625200310.GC7898@sasha-vm \
    --to=sashal@kernel.org \
    --cc=bryankel@microsoft.com \
    --cc=corbet@lwn.net \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=rdunlap@infradead.org \
    --cc=sumit.garg@linaro.org \
    --cc=tee-dev@lists.linaro.org \
    --cc=thiruan@microsoft.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 NNTP newsgroup(s).