From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<op-tee@lists.trustedfirmware.org>
Subject: Re: [RFC PATCH 0/4] introduction of a remoteproc tee to load signed firmware images
Date: Tue, 30 May 2023 19:12:21 +0200 [thread overview]
Message-ID: <fc7fcb92-dec6-413a-7b08-1083a444f6fc@foss.st.com> (raw)
In-Reply-To: <ZHYiYGMHdqxBaDzc@p14s>
Hello Mathieu,
On 5/30/23 18:20, Mathieu Poirier wrote:
> On Tue, May 23, 2023 at 11:13:46AM +0200, Arnaud Pouliquen wrote:
>> This RFC proposes an implementation of a remoteproc tee driver to
>> communicate with a TEE trusted application in charge of authenticating
>> and loading remoteproc firmware image in an Arm secure context.
>>
>> The services implemented are the same as those offered by the Linux
>> remoteproc framework:
>> - load of a signed firmware
>> - start/stop of a coprocessor
>> - get the resource table
>>
>>
>> The OP-TEE code in charge of providing the service in a trusted application
>> is proposed for upstream here:
>> https://github.com/OP-TEE/optee_os/pull/6027
>>
>> For more details on the implementation a presentation is available here:
>> https://resources.linaro.org/en/resource/6c5bGvZwUAjX56fvxthxds
>>
>> Arnaud Pouliquen (4):
>> tee: Re-enable vmalloc page support for shared memory
>> remoteproc: Add TEE support
>> dt-bindings: remoteproc: add compatibility for TEE support
>> remoteproc: stm32: Add support of an OP-TEE TA to load the firmware
>>
>> .../bindings/remoteproc/st,stm32-rproc.yaml | 33 +-
>> drivers/remoteproc/Kconfig | 9 +
>> drivers/remoteproc/Makefile | 1 +
>> drivers/remoteproc/stm32_rproc.c | 234 +++++++++--
>> drivers/remoteproc/tee_remoteproc.c | 397 ++++++++++++++++++
>> drivers/tee/tee_shm.c | 24 +-
>> include/linux/tee_remoteproc.h | 101 +++++
>> 7 files changed, 753 insertions(+), 46 deletions(-)
>> create mode 100644 drivers/remoteproc/tee_remoteproc.c
>> create mode 100644 include/linux/tee_remoteproc.h
>
> Looking at comments from Christoph, there seems to be a good refactoring
> exercise in store for this pathset.
Yes, a good opportunity to ramp-up on kernel memory management :)
As such I will wait for the next revision
> to look at it.
That's fair. More than that I would prefer to focus first on OP-TEE part that
provides the service. The OP-TEE pull request review could have significant
impacts on the kernel implementation...
Thanks,
Arnaud
>
> Thanks,
> Mathieu
>
>>
>> --
>> 2.25.1
>>
prev parent reply other threads:[~2023-05-30 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 9:13 [RFC PATCH 0/4] introduction of a remoteproc tee to load signed firmware images Arnaud Pouliquen
2023-05-23 9:13 ` [RFC PATCH 1/4] tee: Re-enable vmalloc page support for shared memory Arnaud Pouliquen
2023-05-24 6:46 ` Christoph Hellwig
2023-05-24 14:01 ` Arnaud POULIQUEN
2023-05-26 12:37 ` Christoph Hellwig
2023-05-29 7:17 ` Arnaud POULIQUEN
2023-05-23 9:13 ` [RFC PATCH 2/4] remoteproc: Add TEE support Arnaud Pouliquen
2023-05-24 6:50 ` Christoph Hellwig
2023-05-23 9:13 ` [RFC PATCH 3/4] dt-bindings: remoteproc: add compatibility for " Arnaud Pouliquen
2023-05-30 11:50 ` Krzysztof Kozlowski
2023-05-30 15:00 ` Arnaud POULIQUEN
2023-05-30 15:12 ` Krzysztof Kozlowski
2023-05-23 9:13 ` [RFC PATCH 4/4] remoteproc: stm32: Add support of an OP-TEE TA to load the firmware Arnaud Pouliquen
2023-05-30 16:20 ` [RFC PATCH 0/4] introduction of a remoteproc tee to load signed firmware images Mathieu Poirier
2023-05-30 17:12 ` Arnaud POULIQUEN [this message]
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=fc7fcb92-dec6-413a-7b08-1083a444f6fc@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=andersson@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mathieu.poirier@linaro.org \
--cc=op-tee@lists.trustedfirmware.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