From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Maxim Uvarov <maxim.uvarov@linaro.org>
Cc: linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org,
peterhuewe@gmx.de, jgg@ziepe.ca, gregkh@linuxfoundation.org,
jens.wiklander@linaro.org, linux-integrity@vger.kernel.org,
arnd@linaro.org, sumit.garg@linaro.org
Subject: Re: [PATCHv5 1/3] optee: do drivers initialization before and after tee-supplicant run
Date: Mon, 1 Jun 2020 04:49:01 +0300 [thread overview]
Message-ID: <20200601014901.GB794847@linux.intel.com> (raw)
In-Reply-To: <20200529082701.13457-2-maxim.uvarov@linaro.org>
On Fri, May 29, 2020 at 11:26:59AM +0300, Maxim Uvarov wrote:
> Some drivers (like ftpm) can operate only after tee-supplicant
> runs because of tee-supplicant provides things like storage
> services. This patch splits probe of non tee-supplicant dependable
> drivers to the early stage, and after tee-supplicant run probe other
> drivers.
>
> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>
> Suggested-by: Sumit Garg <sumit.garg@linaro.org>
> Suggested-by: Arnd Bergmann <arnd@linaro.org>
$ scripts/get_maintainer.pl drivers/tee
Jens Wiklander <jens.wiklander@linaro.org> (maintainer:TEE SUBSYSTEM)
tee-dev@lists.linaro.org (open list:TEE SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
tee-dev is missing. Please resend.
/Jarkko
next prev parent reply other threads:[~2020-06-01 1:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 8:26 [PATCHv5 0/3] optee: register drivers on optee bus Maxim Uvarov
2020-05-29 8:26 ` [PATCHv5 1/3] optee: do drivers initialization before and after tee-supplicant run Maxim Uvarov
2020-06-01 1:49 ` Jarkko Sakkinen [this message]
2020-06-01 7:13 ` Maxim Uvarov
2020-06-01 7:59 ` Jarkko Sakkinen
2020-06-01 10:45 ` Sumit Garg
2020-05-29 8:27 ` [PATCHv5 2/3] optee: use uuid for sysfs driver entry Maxim Uvarov
2020-06-01 10:17 ` Sumit Garg
2020-05-29 8:27 ` [PATCHv5 3/3] tpm_ftpm_tee: register driver on TEE bus Maxim Uvarov
2020-06-01 11:11 ` Sumit Garg
2020-06-01 14:06 ` Maxim Uvarov
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=20200601014901.GB794847@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).