Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Not Answered
  • Locked Locked
  • Replies 0 replies
  • Subscribers 347 subscribers
  • Views 1548 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What is ARM CPU known state?

YOO JEUNGWOO

In the PSCI Specification, "CPU know state" is mentioned several times. For example,

  • The caller must place all cores in a known state prior to the call. Like all other APIs presented here, the calls can only originate in the Normal world. On a SYSTEM_OFF call the implementation completely removes power from highest power level. The following start must be a cold boot from the point of view of the caller.
  • One way in which cores can be placed into a known state is to use calls to CPU_OFF on all online cores except for the last one, which instead uses SYSTEM_OFF. If a UP Trusted OS is present, this method only works if the core that calls SYSTEM_OFF is the one where the Trusted OS is resident, as calls to CPU_OFF on this core return a DENIED error. Any core can call SYSTEM_OFF.

I can see one of the examples of the CPU known state is "CPU OFF". However, can not find a clear definition or requirement of the CPU's known state. Does anybody know what is the CPU's known state?