openstlinux/uboot-st
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

dt-bindings: arm: scmi: OP-TEE as transport channel for SCMI messages

Browse Source 
Introduce compatible "linaro,scmi-optee" for SCMI transport channel
based on an OP-TEE service invocation.

Define "linaro,optee-channel-id" property to identify the OP-TEE SCMI
channel used by the protocol(s). OP-TEE SCMI transport can either use
shared memory or a static shared memory buffer identified by the DT.

These bindings were posted to the Linux kernel DT bindings mailing list
and acked by maintainer [1].

[Backport of commit fcb41d4db2 ("dt-bindings: arm: scmi: OP-TEE as transport channel for SCMI messages")]

Link: [1] https://lore.kernel.org/linux-arm-kernel/20211029102118.GG6526@e120937-lin/T/
Cc: Jaehoon Chung <jh80.chung@samsung.com>
Reviewed-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
Change-Id: I03756231fc4e44827847fcfa5da66e19591f4a29
This commit is contained in:
Etienne Carriere
2021-11-09 17:08:23 +01:00
committed by Patrick Delaunay
parent ec76df3f7c
commit 3a64abd3fd
1 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/device-tree-bindings/arm/arm,scmi.txt
View File

@ -14,7 +14,8 @@ Required properties:
The scmi node with the following properties shall be under the /firmware/ node. The scmi node with the following properties shall be under the /firmware/ node.
- compatible : shall be "arm,scmi" or "arm,scmi-smc" for smc/hvc transports - compatible : shall be "arm,scmi" or "arm,scmi-smc" for smc/hvc transports,
or "linaro,scmi-optee" for OP-TEE transport.
- mboxes: List of phandle and mailbox channel specifiers. It should contain - mboxes: List of phandle and mailbox channel specifiers. It should contain
exactly one or two mailboxes, one for transmitting messages("tx") exactly one or two mailboxes, one for transmitting messages("tx")
and another optional for receiving the notifications("rx") if and another optional for receiving the notifications("rx") if
@ -26,6 +27,8 @@ The scmi node with the following properties shall be under the /firmware/ node.
- #size-cells : should be '0' as 'reg' property doesn't have any size - #size-cells : should be '0' as 'reg' property doesn't have any size
associated with it. associated with it.
- arm,smc-id : SMC id required when using smc or hvc transports - arm,smc-id : SMC id required when using smc or hvc transports
- linaro,optee-channel-id : Channel specifier required when using OP-TEE
transport.
Optional properties: Optional properties:
@ -33,16 +36,16 @@ Optional properties:
See Documentation/devicetree/bindings/mailbox/mailbox.txt for more details See Documentation/devicetree/bindings/mailbox/mailbox.txt for more details
about the generic mailbox controller and client driver bindings. about the generic mailbox controller and client driver bindings.
The mailbox is the only permitted method of calling the SCMI firmware.
Mailbox doorbell is used as a mechanism to alert the presence of a Mailbox doorbell is used as a mechanism to alert the presence of a
messages and/or notification. messages and/or notification.
Each protocol supported shall have a sub-node with corresponding compatible Each protocol supported shall have a sub-node with corresponding compatible
as described in the following sections. If the platform supports dedicated as described in the following sections. If the platform supports dedicated
communication channel for a particular protocol, the 3 properties namely: communication channel for a particular protocol, properties shall be present
mboxes, mbox-names and shmem shall be present in the sub-node corresponding in the sub-node corresponding to that protocol. These properties are:
to that protocol. - mboxes, mbox-names and shmem for mailbox transport
- arm,smc-id and shmem for smc/hvc transport
- linaro,optee-channel-id and possibly shmem for OP-TEE transport
Clock/Performance bindings for the clocks/OPPs based on SCMI Message Protocol Clock/Performance bindings for the clocks/OPPs based on SCMI Message Protocol
------------------------------------------------------------ ------------------------------------------------------------