u-boot.git/drivers/tee/optee/core.c, branch v2024.01

tee: optee: fix uuid comparisons on service discovery

2023-01-20T08:04:56Z

When comparing UUIDs for discovered services we only compare up to the ptr size instead of the entire UUID Fixes: 94ccfb78a4d61 ("drivers: tee: optee: discover OP-TEE services") Signed-off-by: Ilias Apalodimas Reviewed-by: Etienne Carriere Reviewed-by: Jens Wiklander

tee: optee: fix a print error on rng probing

2023-01-20T08:04:56Z

If we fail to probe the optee-rng device, we print a wrong message referring to the firmware tpm. Fixes: 476a3d58dfeb ("tee: optee: don't fail probe because of optee-rng") Reviewed-by: Patrick Delaunay Reviewed-by: Etienne Carriere Reviewed-by: Jens Wiklander Signed-off-by: Ilias Apalodimas

optee: bind the TA drivers on OP-TEE node

2023-01-11T20:02:24Z

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 Reviewed-by: Patrice Chotard

tee: optee: discover services dependent on tee-supplicant

2022-12-23T08:26:15Z

Makes OP-TEE to enumerate also services depending on tee-supplicant support in U-Boot. This change allows OP-TEE services like fTPM TA to be discovered and get a TPM device registered in U-Boot. Signed-off-by: Etienne Carriere Reviewed-by: Ilias Apalodimas Reviewed-by: Jens Wiklander Signed-off-by: Ilias Apalodimas

tee: optee: don't fail probe because of optee-rng

2022-12-23T08:26:11Z

Fixes optee-rng driver bind sequence in optee driver to print a warning message but not report an error status when a optee-rng service driver fails to be bound as the optee driver itself is still fully functional. Signed-off-by: Etienne Carriere Reviewed-by: Ilias Apalodimas Reviewed-by: Jens Wiklander Signed-off-by: Ilias Apalodimas

drivers: tee: optee: discover OP-TEE services

2022-09-14T19:23:03Z

This change defines resources for OP-TEE service drivers to register themselves for being bound to when OP-TEE firmware reports the related service is supported. OP-TEE services are discovered during optee driver probe sequence which mandates optee driver is always probe once bound. Discovery of optee services and binding to related U-Boot drivers is embedded upon configuration switch CONFIG_OPTEE_SERVICE_DISCOVERY. Cc: Jens Wiklander Cc: Patrick Delaunay Signed-off-by: Etienne Carriere Reviewed-by: Patrick Delaunay

drivers: tee: optee: remove unused probe local variable

2022-09-14T19:23:03Z

Removes local variable child in optee_probe() that is not used. Cc: Patrick Delaunay Reviewed-by: Patrick Delaunay Signed-off-by: Etienne Carriere

tee: optee: bind rng optee driver

2022-04-11T14:28:04Z

In U-Boot, the discovery of TA based on its UUID on the TEE bus is not supported. This patch only binds the driver associated to the new supported OP-TEE TA = TA_HWRNG when this driver is enable. Signed-off-by: Patrick Delaunay

tee: optee: sync cache on pre-reloc OP-TEE invocation

2021-07-23T11:13:25Z

This change ensures both U-Boot and OP-TEE see the same content from shared memory when OP-TEE is invoked prior U-Boot relocation. This change is required since U-Boot may execute with data cache off while OP-TEE always enables cache on memory shared with U-Boot. Signed-off-by: Etienne Carriere Reviewed-by: Jens Wiklander Acked-by: Ilias Apalodimas

tee: optee: Change printing during optee_probe

2021-04-12T21:44:55Z

Right now the error messages when optee has a version mismatch or shared memory is not configured are done with a debug(). That's not very convenient since you have to enable debugging to figure out what's going on, although this is an actual error. So let's switch the debug() -> dev_err() and report those explicitly. Signed-off-by: Ilias Apalodimas Reviewed-by: Patrick Delaunay