From: Tom Rini <trini@konsulko.com>
To: Etienne Carriere <etienne.carriere@linaro.org>
Cc: u-boot@lists.denx.de,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Patrice Chotard <patrice.chotard@foss.st.com>
Subject: Re: [PATCH v2 01/14] firmware: scmi: optee: use TEE shared memory for SCMI messages
Date: Thu, 23 Jun 2022 14:32:28 -0400 [thread overview]
Message-ID: <20220623183228.GI2484912@bill-the-cat> (raw)
In-Reply-To: <20220531160929.931150-2-etienne.carriere@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On Tue, May 31, 2022 at 06:09:16PM +0200, Etienne Carriere wrote:
> Changes implementation when using TEE dynamically allocated shared
> memory to synchronize with the Linux implementation where the legacy
> SMT protocol cannot be used with such memory since it is expected from
> device mapped memory whereas OP-TEE shared memory is cached and
> hence should not be accessed using memcpy_toio()/memcpy_fromio().
>
> This change implements the MSG shared memory protocol introduced
> in Linux [1]. The protocol uses a simplified SMT header of 32bit
> named MSG_SMT to carry SCMI protocol information and uses side channel
> means to carry exchanged buffer size information, as TEE invocation API
> parameters when used in the SCMI OP-TEE transport.
>
> Link: [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f301bba0ca7392d16a6ea4f1d264a91f1fadea1a
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
For the series, 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-06-23 18:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 16:09 [PATCH v2 00/14] SCMI multi-channel and optee shm Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 01/14] firmware: scmi: optee: use TEE shared memory for SCMI messages Etienne Carriere
2022-06-23 18:32 ` Tom Rini [this message]
2022-05-31 16:09 ` [PATCH v2 02/14] firmware: scmi: optee: fix inline description of PTA_SCMI_CMD_GET_CHANNEL Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 03/14] firmware: scmi: prepare scmi uclass API to multi-channel Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 04/14] firmware: scmi: prepare uclass to pass channel reference Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 05/14] firmware: scmi: factorize scmi transport look up Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 06/14] firmware: scmi: add multi-channel support Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 07/14] firmware: scmi: mailbox transport: implement multi-channel Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 08/14] firmware: scmi: smccc " Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 09/14] firmware: scmi: optee " Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 10/14] clk: scmi: support SCMI multi-channel Etienne Carriere
2022-09-28 17:29 ` Sean Anderson
2022-05-31 16:09 ` [PATCH v2 11/14] reset: " Etienne Carriere
2022-05-31 16:09 ` [PATCH v2 12/14] power: regulator: " Etienne Carriere
2022-06-14 2:13 ` Jaehoon Chung
2022-05-31 16:09 ` [PATCH v2 13/14] power: regulator: scmi: simplify scmi_voltd_set_enable() Etienne Carriere
2022-06-14 2:13 ` Jaehoon Chung
2022-05-31 16:09 ` [PATCH v2 14/14] firmware: scmi: use multi channel in mailbox, optee and smccc agents Etienne Carriere
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=20220623183228.GI2484912@bill-the-cat \
--to=trini@konsulko.com \
--cc=etienne.carriere@linaro.org \
--cc=patrice.chotard@foss.st.com \
--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