Re: [PATCH v21 0/6] Introduction of a remoteproc tee to load signed firmware
Krzysztof Kozlowski via OP-TEE <[email protected]>
| Newsgroups | org.trustedfirmware.lists.op-tee,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-remoteproc |
|---|---|
| Message-ID | <20260319-fiery-onyx-serval-aceb17@quoll> |
On Tue, Mar 17, 2026 at 07:03:21PM +0100, Arnaud Pouliquen wrote:
>
> Main updates from version V20[4]:
> --------------------------------
> To address Rob’s concern on v20concerning resource declaration under the
> tee node, the device tree is now structured as follows,replacing the
> child-parent hierarchy with a phandle:
>
> firmware {
> tee_rproc: optee-rproc {
> compatible = "80a4c275-0a47-4905-8285-1486a9771a08";
> };
> };
>
And what is the parent here?
> m4: m4@0 {
What sort of bus do you have here (IOW, what does this 0 mean?)
> compatible = "st,stm32mp1-m4-tee";
> reg = <0 0>;
>
> mboxes = <&ipcc 0>, <&ipcc 1>, <&ipcc 2>;
> mbox-names = "vq0", "vq1", "shutdown";
>
> memory-region = <&vdev0vring0>, <&m_ipc_shm>, <&mcuram2>,
> <&vdev0vring1>, <&vdev0buffer>, <&retram>;
>
> interrupt-parent = <&exti>;
> interrupts = <68 1>;
>
> rproc-tee-phandle = <&tee_rproc 0>;
> st,auto-boot;
> wakeup-source;
>
> status = "okay";
> };
Best regards,
Krzysztof