On Wed, Dec 17, 2025 at 04:39:12PM +0100, Arnaud Pouliquen wrote: > Add a device tree binding for the TEE-based remote processor control > service implemented as an OP-TEE Trusted Application identified by > UUID 80a4c275-0a47-4905-8285-1486a9771a08. > > The TEE service node is a child of the "linaro,optee-tz" firmware node and > acts as a container for remoteproc devices that are controlled via TEE.
Is this generic for any remoteproc device or just ST's remoteproc. Looks like the latter to me. > In addition, the "linaro,optee-tz" binding is updated to specify the > '#address-cells' and '#size-cells' values used for child TEE service > nodes. I'm pretty sure I already rejected per service/app child nodes for OP-TEE when its binding was submitted. If we do need something in DT to define some resources, then can't we have some sort of standard/common communications channel? I don't care to see some sort of free-for-all where we have every vendor doing their own thing. OP-TEE needs to standarize this. Rob
