-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add save/restore support to ARC core #2710
Comments
by Qiu Peiyang: Board= quark_se_c1000_devboard I cherry-pick the four patches related to PM on ARC core, and then run tests/power/power_states. Quark SE: Power Management sample application |
by Julien Delayen: Hi Peiyang, I did the check on my side and did not see that behavior. (make BOARD=quark_se_c1000_devboard) I am running this test on a Quark SE board, not on a arduino 101. Those patches are enabling the ARC feature. In order to test this, you need to: Flash the x86 side with the hello world sample with CONFIG_ARC_INIT=y. This will be fixed once GH-2604 is implemented as some support needs to be added to |
by Sharron LIU: With a "start_arc" binary shared by developer, I was able to verify the ARC context save/restore across deep sleep @quark_se platforms with QMSI v1.3+ ROM. go to sleep via _sys_soc_set_power_state() and wake up from AONPTsuspend/resume system clock device across deep sleepCPU and register context save/restore across deep sleepThe test case is still kept locally, as the integration test is still pending on GH-2604 to get ARC deep sleep and wake up in sync with X86 core. Closing this. Thanks. |
by Mark Linkmeyer: Fixing incorrect priority |
Reported by Julien Delayen:
When restoring from sleep, the x86 core will start the ARC core which will need
to restore its context (registers, program counter).
The ARC shim layer will support sleep and deep sleep and the power
sample will be supporting the ARC.
This does not involve any type of communication between the core and
assumes the x86 is ready to en ter sleep at any time.
The communication will be treated as a separate story.
(Imported from Jira ZEP-1222)
The text was updated successfully, but these errors were encountered: