u-boot/drivers/tee
Patrick Delaunay 59dacc3190 optee: bind the TA drivers on OP-TEE node
In U-Boot driver model the devices can be referenced by
phandle in the U-Boot configuration nodes.

Without a valid node provided during the bind, the driver
associated to OP-TEE TA can't be referenced.

For example to force the sequence number with alias
(.flags = DM_UC_FLAG_SEQ_ALIAS)

 	aliases {
		rng0 = &optee;
 	};

or other configuration:

board-sysinfo {
   compatible = "vendor,sysinfo-board";
   ramdom = <&optee>;
}

With this patch all drivers bound from OP-TEE service
discovery are now associated are associated to OP-TEE
node, allowing to identify by phandle the driver
provided by the TA for one UCLASS without modifying
device tree.

Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
2023-01-11 15:02:24 -05:00
..
broadcom drivers: tee: broadcom: add optee based bnxt fw load driver 2020-07-29 10:37:11 -04:00
optee optee: bind the TA drivers on OP-TEE node 2023-01-11 15:02:24 -05:00
Kconfig drivers: tee: broadcom: add optee based bnxt fw load driver 2020-07-29 10:37:11 -04:00
Makefile drivers: tee: sandbox: add rpc test ta emulation 2021-02-16 11:48:20 -05:00
sandbox.c drivers: tee: sandbox: SCP03 control emulator 2021-03-14 11:50:13 -04:00
tee-uclass.c tee: optee: sync cache on pre-reloc OP-TEE invocation 2021-07-23 07:13:25 -04:00