optee: bind the TA drivers on OP-TEE node
authorPatrick Delaunay <patrick.delaunay@foss.st.com>
Thu, 15 Dec 2022 08:54:52 +0000 (09:54 +0100)
committerTom Rini <trini@konsulko.com>
Wed, 11 Jan 2023 20:02:24 +0000 (15:02 -0500)
commit59dacc319030748817b28cce9c773e15f2b73dc8
treec69b4b359ab7849c88082fffccaba02e4cfe0fed
parent1c44d1087925263a428bee68d30ac9dec6f224e5
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>
drivers/tee/optee/core.c