Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp48814ybd; Tue, 25 Jun 2019 16:14:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqwdjg0RnrEe0o4w9z9QtWrJLnylnb1cpiW6sZhJi4RnkP1xnn8xQj18n66ywsI5PSkE160l X-Received: by 2002:a65:4cc4:: with SMTP id n4mr13801230pgt.307.1561504493925; Tue, 25 Jun 2019 16:14:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561504493; cv=none; d=google.com; s=arc-20160816; b=hMTYuLVZrgHpg7+Y+yodMl2XYKoUn8i4HrXFgwk5xAnt96TnebnO9VpVLhKf5KiNSq E0BZdNQU72IrzYWRsd48t2zorfljSR+ErmFmndFGSSHSWRrnZwEezkudYm667APfGgok wtrtEEtu+zxrjrFSONDpMmEcpmTV9TFwlkqcUWW7MlzTAkrtsSf/EYKUq5+5xq98dnMF eZoFjKgyK0r0Kg1C9yb7rD5UmXL9FH0oROG0lS3LBKSHXzwg4y2ZTHCq2H6kWGlyUZSX nodsFLUNLsXjEqIL5mD278ac2uBGgVjN77x78IemLZOVqtZVMQ9nAM7jB51+n4J7lMz/ Sohg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=bNOnF9RPhjENVHpzmRNMIxdtfQ6guu6sKYduKcd0Tc8=; b=JYN37goctQ6j5GjPa64GK8h0F8hpBsfl96TNXiUNNSMdcHYESoZHkUdSN/E0hryFL6 3DcFa9JVSLtz7s8Gt47ftUIxc+Jo4con50MFkEwHtVVco4Jr/QAHlnjC1MNjYnr22/KC 2d4v375twAjNIjvoAcV1/0QuVt5Vb0r43B/Lre2YnDrsI85g0zIiGwrPxvB7aLnc+det 9eH4om6Uj9mydzphqda10e+wbXOoJipKBC2VNpRImC0cXTcno2X6qFBc9yw4+n3bLC/X yxPFkL6U2Q7T83iC6BxfNVr6v6LLt8XRE8afiT7Tt2rCFE42i8ZWHHwXbPIDlhZ57f8w v7cw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=V8VlTO0p; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o26si13980795pgv.311.2019.06.25.16.14.35; Tue, 25 Jun 2019 16:14:53 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=V8VlTO0p; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726396AbfFYXNm (ORCPT + 99 others); Tue, 25 Jun 2019 19:13:42 -0400 Received: from merlin.infradead.org ([205.233.59.134]:36102 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726068AbfFYXNm (ORCPT ); Tue, 25 Jun 2019 19:13:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=bNOnF9RPhjENVHpzmRNMIxdtfQ6guu6sKYduKcd0Tc8=; b=V8VlTO0pZvD95eJUQjucRK+Rbt gO6Y2d2E1MYhOhgMoiK3mYh9wHSdrc7Y4RDWpU/WgZkXW/HbILKz+9VWOpeI9mPPdnknTiW1HEKmV 4k2j/uzhDJ5RvVDLUMKJ/GWftlXZ9kVhW9SIARyQtBryfonYWlwrQEc+/ZyNatSQoYKsk1LJlFY8c zzEQVzP1oauTdWdXBJAefgElIT0JIzbQZ9zS4iUz30xXrqHmwtOKKzcgDbTgf4tSTRmtk2Z/KS58W mEdk/ljHdt/Sh9+G4tZ7hzAqyp1+wAIvnG1y9Wvm+N4pNWeEb7VWyNLOoIDy7mEmxqeGMgTEoli91 0XodM4TQ==; Received: from static-50-53-52-16.bvtn.or.frontiernet.net ([50.53.52.16] helo=midway.dunlab) by merlin.infradead.org with esmtpsa (Exim 4.92 #3 (Red Hat Linux)) id 1hfud4-0001Kq-Oz; Tue, 25 Jun 2019 23:13:35 +0000 Subject: Re: [PATCH v7 2/2] fTPM: add documentation for ftpm driver To: Sasha Levin , peterhuewe@gmx.de, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca Cc: 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 References: <20190625201341.15865-1-sashal@kernel.org> <20190625201341.15865-3-sashal@kernel.org> From: Randy Dunlap Message-ID: Date: Tue, 25 Jun 2019 16:13:32 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <20190625201341.15865-3-sashal@kernel.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/25/19 1:13 PM, Sasha Levin wrote: > This patch adds basic documentation to describe the new fTPM driver. > > Signed-off-by: Sasha Levin Acked-by: Randy Dunlap Thanks. > --- > 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..48de0dcec0f6 > --- /dev/null > +++ b/Documentation/security/tpm/tpm_ftpm_tee.rst > @@ -0,0 +1,31 @@ > +============================================= > +Firmware TPM Driver > +============================================= > + > +| Authors: > +| Thirupathaiah Annapureddy > +| Sasha Levin > + > +This document describes the firmware Trusted Platform Module (fTPM) > +device driver. > + > +Introduction > +============ > + > +This driver is a shim for firmware implemented in ARM's TrustZone > +environment. The driver allows programs to interact with the TPM in the same > +way they would interact with a hardware TPM. > + > +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 > +through this device. > -- ~Randy