https://url4.org/ncmhp
https://url4.org/kbhiz
https://url4.org/evpsc
https://url4.org/dvkzn
https://url4.org/lufcx

I learned absolutely everything about my question when I read this post, thanks to the author for the detailed description. I wrote my review on the https://paperwritingservices.reviews/ , you can go in and read. Thank you very much for your attention and your time.

Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin https://ukbestessays.org/ from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia

Thanks to the creator for writing the post, it was quite necessary for me and liked it. I wrote a note on the https://essaysservicesreviews.com/ about this. I will be happy if you read it and accept it. Thank you for your concern.

Thanks for your reply. It is difficult to submit code to community or Gerrit using company's account and system. So, I wonder whether it's permitted to upload by providing modifications or “git send-email” with patches.

The whole problem has boiled down to a flash write issue and it has been worked around by c32710c7fc8514dd0d072a01549e23a94278ee17.

Verified with https://github.com/zephyrproject-rtos/zephyr/pull/30226

This issue is now fixed and can be closed

Hi Li,

Hi,
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:

Yes, The power domain topology of the system can be described as 8 sockets, each socket with 10 clusters and each cluster with 8 cores. We just consider a system like this might face the constraint mentioned above, and we must modify the declaration of lock_index to solve this problem. Feature, more and more interconnected system, with numerous cpus, might face the same problem.

Hi,
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.

Patch fixed and merged

Fixed by merge of https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6604