From: Tom Rini <trini@konsulko.com>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: u-boot@lists.denx.de, Jens Wiklander <jens.wiklander@linaro.org>,
Patrick Delaunay <patrick.delaunay@foss.st.com>
Subject: Re: [PATCH v5 2/3] drivers: tee: optee: discover OP-TEE services
Date: Thu, 15 Sep 2022 10:01:53 -0400 [thread overview]
Message-ID: <20220915140153.GC6993@bill-the-cat> (raw)
In-Reply-To: <20220726142143.1739265-2-etienne.carriere@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On Tue, Jul 26, 2022 at 04:21:42PM +0200, Etienne Carriere wrote:
> This change defines resources for OP-TEE service drivers to register
> themselves for being bound to when OP-TEE firmware reports the related
> service is supported. OP-TEE services are discovered during optee
> driver probe sequence which mandates optee driver is always probe once
> bound.
>
> Discovery of optee services and binding to related U-Boot drivers is
> embedded upon configuration switch CONFIG_OPTEE_SERVICE_DISCOVERY.
>
> Cc: Jens Wiklander <jens.wiklander@linaro.org>
> Cc: Patrick Delaunay <patrick.delaunay@foss.st.com>
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
> Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-09-15 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 14:21 [PATCH v5 1/3] drivers: tee: optee: remove unused probe local variable Etienne Carriere
2022-07-26 14:21 ` [PATCH v5 2/3] drivers: tee: optee: discover OP-TEE services Etienne Carriere
2022-09-15 14:01 ` Tom Rini [this message]
2022-07-26 14:21 ` [PATCH v5 3/3] drivers: rng: optee_rng: register to CONFIG_OPTEE_SERVICE_DISCOVERY Etienne Carriere
2022-09-15 14:02 ` Tom Rini
2022-09-15 14:01 ` [PATCH v5 1/3] drivers: tee: optee: remove unused probe local variable Tom Rini
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=20220915140153.GC6993@bill-the-cat \
--to=trini@konsulko.com \
--cc=etienne.carriere@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=patrick.delaunay@foss.st.com \
--cc=u-boot@lists.denx.de \
/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