linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Cc: Sumit Garg <sumit.garg@linaro.org>,
	Maxim Uvarov <maxim.uvarov@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	tee-dev@lists.linaro.org, op-tee@lists.trustedfirmware.org,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] optee bus for v5.9
Date: Fri, 10 Jul 2020 10:52:30 +0200	[thread overview]
Message-ID: <20200710085230.GA1312913@jade> (raw)

Hello arm-soc maintainers,

Please pull these patches enabling multi-stage OP-TEE bus enumeration
and also adds a TPM driver for a OP-TEE based fTPM Trusted Application.

The TPM driver depends on and takes advantage of the multi-stage OP-TEE bus
enumeration by indicating that it should be probed after tee-supplicant has
been started.

Jarkko, one of the TPM maintainers, has been involved in reviewing these
patches and agrees that I can include the TPM patch in the pull request.

Thanks,
Jens

The following changes since commit 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162:

  Linux 5.7 (2020-05-31 16:49:15 -0700)

are available in the Git repository at:

  git://git.linaro.org/people/jens.wiklander/linux-tee.git tags/optee-bus-for-v5.9

for you to fetch changes up to 9f1944c23c8cb1c033b73de80cf6c612a2a80a2b:

  tpm_ftpm_tee: register driver on TEE bus (2020-07-10 09:41:58 +0200)

----------------------------------------------------------------
Enable multi-stage OP-TEE bus enumeration

Probes drivers on the OP-TEE bus in two steps. First for drivers which
do not depend on tee-supplicant. After tee-supplicant has been started
probe the devices which do depend on tee-supplicant.

Also introduces driver which uses an OP-TEE based fTPM Trusted
Application depends on tee-supplicant NV RAM implementation based on
RPMB secure storage.

----------------------------------------------------------------
Maxim Uvarov (3):
      optee: use uuid for sysfs driver entry
      optee: enable support for multi-stage bus enumeration
      tpm_ftpm_tee: register driver on TEE bus

 Documentation/ABI/testing/sysfs-bus-optee-devices |  8 +++
 MAINTAINERS                                       |  1 +
 drivers/char/tpm/tpm_ftpm_tee.c                   | 70 +++++++++++++++++++----
 drivers/tee/optee/core.c                          | 27 ++++++++-
 drivers/tee/optee/device.c                        | 38 ++++++------
 drivers/tee/optee/optee_private.h                 | 10 +++-
 6 files changed, 119 insertions(+), 35 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-optee-devices

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-07-10  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  8:52 Jens Wiklander [this message]
2020-07-10 11:00 ` [GIT PULL] optee bus for v5.9 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=20200710085230.GA1312913@jade \
    --to=jens.wiklander@linaro.org \
    --cc=arm@kernel.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxim.uvarov@linaro.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=soc@kernel.org \
    --cc=sumit.garg@linaro.org \
    --cc=tee-dev@lists.linaro.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).