- User Since
- Apr 5 2019, 4:17 PM (128 w, 4 d)
Dec 2 2020
A developer submitted a patch which closely relates to this issue. Please give your feedback here: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/7314
Nov 30 2020
Please use personal email and git configs/identity to push the patch to trustedfirmware.org. Few developers from the tf-a community have done this. Here is a link to contribution guidelines:
Nov 19 2020
Yeah, looks like such a large system with numerous clusters will run into an issue with the current limitation of "lock_index" being "unsigned char". Please go ahead and submit a patch for review:
Nov 18 2020
The struct "non_cpu_pwr_domain_node" represents a non-leaf power domain in an SoC such as a logical cluster. As you mentioned, the lock_index declaration with "unsigned char" limits such non-cpu power domains to 64. I believe it doesn't restrict the number of CPUs in a system to be <= 64. Do you currently face an issue with PSCI implementation due to the above constraint? Can you advise what is the power domain topology of your system? I think the lock_index can be expanded using "unsigned int" if needed.
Jan 6 2020
I was able to compile TF-A for rk3328 platform using the same command and specifying the CROSS_COMPILE as aarch64-linux-gnu-
I use the publicly available toolchain https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads .In this case, I specifically used the 8.3 x86_64 Linux hosted cross compiler in my Ubuntu 18.04 (Virtual Box image ).
If I am not wrong, you dont have to use a cross compiler. However, I dont have access to a native Arm machine to test your build command. What compiler did you use?