From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Maxim Uvarov <maxim.uvarov@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"tee-dev @ lists . linaro . org" <tee-dev@lists.linaro.org>,
peterhuewe@gmx.de, jgg@ziepe.ca,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
linux-integrity@vger.kernel.org, Arnd Bergmann <arnd@linaro.org>,
Sumit Garg <sumit.garg@linaro.org>
Subject: Re: [PATCHv2 2/2] tpm_ftpm_tee: register driver on TEE bus
Date: Wed, 27 May 2020 22:42:03 +0300 [thread overview]
Message-ID: <81c59da1dc2a255c58e7e338f30285e68b4664d6.camel@linux.intel.com> (raw)
In-Reply-To: <CAD8XO3bmorhde9YaEUrd07U__01NC9wAE1O6ALijASbbJudHPQ@mail.gmail.com>
On Mon, 2020-05-25 at 09:50 +0300, Maxim Uvarov wrote:
> Jakko,
> tee-supplicant application provides state machine over callbacks with
> RPC messages.
> https://github.com/OP-TEE/optee_client/blob/master/tee-supplicant/src/tee_supplicant.c#L614
> It also allocates shm. Without running tee-supplicant
> tee_client_open_session() will fail.
> optee_open_session()->get_msg_arg()->tee_shm_alloc()->...
> Optee team wanted to remove some dependencies from tee-supplicant with
> moving code
> to the kernel. But for now I think that should be out of the scope of
> current patches due to
> they fix driver initialization on tee bus without breaking current
> functionality.
So what is the role in high-level for tee-supplicant? Why does it
exist? No time to dive into code unfortunately.
These kernel commits do not explain in simple terms enough how all
of these entities connect with each other, if you don't have that
understanding beforehand.
/Jarkko
next prev parent reply other threads:[~2020-05-27 19:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 6:47 [PATCHv2 0/2] optee: register drivers on optee bus Maxim Uvarov
2020-05-21 6:47 ` [PATCHv2 1/2] optee: do drivers initialization before and after tee-supplicant run Maxim Uvarov
2020-05-22 11:40 ` Sumit Garg
2020-05-22 12:23 ` Maxim Uvarov
2020-05-24 6:22 ` Jens Wiklander
2020-05-25 7:12 ` Maxim Uvarov
2020-05-21 6:47 ` [PATCH 2/2] tpm_ftpm_tee: register driver on tee bus Maxim Uvarov
2020-05-21 6:47 ` [PATCHv2 2/2] tpm_ftpm_tee: register driver on TEE bus Maxim Uvarov
2020-05-22 17:14 ` Jarkko Sakkinen
2020-05-22 19:29 ` Maxim Uvarov
2020-05-22 20:03 ` Jarkko Sakkinen
2020-05-25 6:50 ` Maxim Uvarov
2020-05-26 9:22 ` Sumit Garg
2020-05-27 19:42 ` Jarkko Sakkinen [this message]
2020-05-28 8:08 ` Maxim Uvarov
2020-05-28 10:11 ` Jens Wiklander
2020-05-29 5:28 ` Sumit Garg
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=81c59da1dc2a255c58e7e338f30285e68b4664d6.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=arnd@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jens.wiklander@linaro.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.uvarov@linaro.org \
--cc=peterhuewe@gmx.de \
--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).