ti: k3: common: Populate BL32 and BL33 entrypoint
ti: k3: common: Populate BL32 and BL33 entrypoint

Because there is no BL2, BL31 must determine the entrypoint and memory
location of BL32 and BL33 on its own.

BL32_BASE and PRELOADED_BL33_BASE will be set in the corresponding board
makefile. We also allow a DTB address to be specified for cases when BL33
is a Linux image.

NOTE: It is possible to pull in this information from device tree as
well, however libfdt does not contain the required hooks to make this
happen at this point in time.

Signed-off-by: Benjamin Fair <ca220295824e288dcaece393af5f2ec059779d5d@ti.com>
Signed-off-by: Nishanth Menon <50c3c575ce2bb12c45e20736ce59e86fe81915b4@ti.com>
Signed-off-by: Andrew F. Davis <a6dfde0ec5c5124d26ab0cb4f9ab9a758dee1d6f@ti.com>

achingupta/arm-trusted-firmware,achingupta/arm-trusted-firmware