From: Tony Lindgren <tony@atomide.com>
To: Keerthy <j-keerthy@ti.com>
Cc: t-kristo@ti.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] omap2: clockdomain: Inroduce cpu_pm notifiers for context save/restore
Date: Thu, 17 May 2018 14:43:47 -0700 [thread overview]
Message-ID: <20180517214347.GR98604@atomide.com> (raw)
In-Reply-To: <1526483821-25585-3-git-send-email-j-keerthy@ti.com>
* Keerthy <j-keerthy@ti.com> [180516 15:21]:
> Inroduce cpu_pm notifiers for context save/restore. This will be
> needed for am43xx family in case of rtc only mode with ddr in
> self-refresh.
...
> +static int cpu_notifier(struct notifier_block *nb, unsigned long cmd, void *v)
> +{
> + switch (cmd) {
> + case CPU_CLUSTER_PM_ENTER:
> + if (enable_off_mode)
> + clkdm_save_context();
> + break;
> + case CPU_CLUSTER_PM_EXIT:
> + if (enable_off_mode)
> + clkdm_restore_context();
> + break;
> + }
> +
> + return NOTIFY_OK;
> +}
Can you do this too only on suspend instead of the cpu notifier?
If you need to call this eventually from cpuidle also then yeah
the notifier makes sense.
Regards,
Tony
next prev parent reply other threads:[~2018-05-17 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 15:16 [PATCH 0/4] arm: mach-omap2: clkdm/pwrdm: Save/restore context Keerthy
2018-05-16 15:16 ` [PATCH 1/4] ARM: OMAP2: Add functions to save and restore clockdomain context en-masse Keerthy
2018-05-16 15:16 ` [PATCH 2/4] omap2: clockdomain: Inroduce cpu_pm notifiers for context save/restore Keerthy
2018-05-17 21:43 ` Tony Lindgren [this message]
2018-05-18 5:57 ` Keerthy
2018-05-18 8:38 ` Tero Kristo
2018-05-18 13:54 ` Tony Lindgren
2018-05-16 15:17 ` [PATCH 3/4] ARM: OMAP2: Add functions to save and restore powerdomain context Keerthy
2018-05-16 15:17 ` [PATCH 4/4] omap2: powerdomain: Inroduce cpu_pm notifiers for context save/restore Keerthy
2018-05-17 21:45 ` Tony Lindgren
2018-05-18 4:32 ` Keerthy
2018-05-18 7:00 ` Tero Kristo
2018-05-18 13:54 ` Tony Lindgren
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=20180517214347.GR98604@atomide.com \
--to=tony@atomide.com \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).