RFCs and P-Rs for building a SCMI server in OP-TEE

[etienne-lms]

Dear SCP-firmware team,

I've created several P-Rs to share changes we need (we at least currently use) to build a SCMI server in optee_os [1].

Scope: In few word, our goal would be to reuse SCP-firmware mainline source files without modification if possible to ease later sync with SCP-firmware future releases. Our aim is to dump needed SCP-firmware source and header files in optee_os source tree and add optee_os specific makefiles (optee_os has a specific build env).

Therefore the following P-Rs and RFCs to propose or simply discuss some changes we made in the sources.

• P-R #381
  Some miscellaneous minor changes that we think could hit mainline.

• P-R #382
  Changes to allow building SCP-firmware resources with some specific configuration disabled (BUILD_HAS_NOTIFICATION, BUILD_HAS_MOD_TIMER, BUILD_HAS_MULTITHREADING).

• RFC #383
  These hacks allowed building SCP-firmware using OP-TEE Core implementation.

• RFC #384
  This RFC shows how we currently bind an OP-TEE thread context with an SCMI thread context. This is used to allow unrelated SCMI services to nicely operate each on their own OP-TEE thread context. Actually this architecture is still being discussed internally.

One can find all these changes applied on v2.7 tag, from https://github.com/etienne-lms/SCP-firmware, branch v2.7-poc-optee. This source tree was dumped in optee_os source tree to have the SCMI server built in OP-TEE Core (kernel).

Regards,
Etienne

[etienne-lms]

superseded by #524