From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: <will@kernel.org>, <mark.rutland@arm.com>
Cc: wangzhe59@huawei.com, Catalin Marinas <catalin.marinas@arm.com>,
huawei.libin@huawei.com, guohanjun@huawei.com,
wangxiongfeng2@huawei.com, linux-arm-kernel@lists.infradead.org
Subject: [Question] About handling PMU context loss in the deepest idle state where the core is powered down
Date: Thu, 9 Jan 2020 10:43:40 +0800 [thread overview]
Message-ID: <d62d9ac1-3af9-b692-a84a-aab4582e5eb8@huawei.com> (raw)
Hi Will, Mark,
Sorry to bother you. It's just that we have come across some problems about PMU recently.
We are working on deep power state on CPU cores. In the deepest idle state, the core will be
powered down. In our implementation, the PMU and the core are in the same power domain,
so the PMU will also be powered down. But I didn't find where we saved the PMU context
in kernel before entering the deepest idle state.
Before we enter the system sleep state, we update the kernel PMU counter and stop the PMU
in 'cpu_pm_pmu_notify()'. But we didn't do that before we enter idle state.
I only find some system registers saving in 'psci_cpu_suspend_enter()->cpu_susend()->cpu_do_suspend()'
Do you have some suggestion about how we can handle this problem ?
Should we save and restore the PMU context before and after the deepest idle state . I don't know
if we can take care of the PMU counters and interrupts properly by saving and restoring
the PMU registers.
Or we should update the kernel counter and stop the PMU, like what we did in system sleep situation.
Or we should let the firmware to handle the saving and restoring problem.
Thanks,
Xiongfeng
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-01-09 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 2:43 Xiongfeng Wang [this message]
2020-01-09 15:03 ` [Question] About handling PMU context loss in the deepest idle state where the core is powered down Will Deacon
2020-01-09 16:46 ` Lorenzo Pieralisi
2020-01-10 3:28 ` Xiongfeng Wang
2020-01-10 3:45 ` Xiongfeng Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d62d9ac1-3af9-b692-a84a-aab4582e5eb8@huawei.com \
--to=wangxiongfeng2@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=huawei.libin@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=wangzhe59@huawei.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox