From: Keerthy <j-keerthy@ti.com>
To: t-kristo@ti.com, sboyd@kernel.org, tony@atomide.com
Cc: linux-clk@vger.kernel.org, d-gerlach@ti.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
j-keerthy@ti.com
Subject: [PATCH v3 4/4] soc: ti: pm33xx: Save/restore clk context based on enable_off_mode setting
Date: Thu, 21 Jun 2018 13:45:07 +0530 [thread overview]
Message-ID: <1529568907-19930-5-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1529568907-19930-1-git-send-email-j-keerthy@ti.com>
Save/restore clk context based on enable_off_mode setting.
The context needs to be saved at the very end of suspend path
and restored at the beginning of resume path.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
No Changes in v2
arch/arm/mach-omap2/pm33xx-core.c | 15 +++++++++++++++
drivers/soc/ti/pm33xx.c | 13 +++++++++++++
include/linux/platform_data/pm33xx.h | 1 +
3 files changed, 29 insertions(+)
diff --git a/arch/arm/mach-omap2/pm33xx-core.c b/arch/arm/mach-omap2/pm33xx-core.c
index 9b3755a..29f848f 100644
--- a/arch/arm/mach-omap2/pm33xx-core.c
+++ b/arch/arm/mach-omap2/pm33xx-core.c
@@ -37,6 +37,20 @@ static int __init am43xx_map_scu(void)
return 0;
}
+static int am43xx_check_off_mode_enable(void)
+{
+ /*
+ * Check for am437x-sk-evm which due to HW design cannot support
+ * this mode reliably.
+ */
+ if (of_machine_is_compatible("ti,am437x-sk-evm") && enable_off_mode) {
+ pr_warn("WARNING: This platform does not support off-mode, entering DeepSleep suspend.\n");
+ return 0;
+ }
+
+ return enable_off_mode;
+}
+
static int amx3_common_init(void)
{
gfx_pwrdm = pwrdm_lookup("gfx_pwrdm");
@@ -161,6 +175,7 @@ static struct am33xx_pm_sram_addr *amx3_get_sram_addrs(void)
.init = am43xx_suspend_init,
.soc_suspend = am43xx_suspend,
.get_sram_addrs = amx3_get_sram_addrs,
+ .check_off_mode_enable = am43xx_check_off_mode_enable,
};
static struct am33xx_pm_platform_data *am33xx_pm_get_pdata(void)
diff --git a/drivers/soc/ti/pm33xx.c b/drivers/soc/ti/pm33xx.c
index 652739c..e749b8d 100644
--- a/drivers/soc/ti/pm33xx.c
+++ b/drivers/soc/ti/pm33xx.c
@@ -6,6 +6,7 @@
* Vaibhav Bedia, Dave Gerlach
*/
+#include <linux/clk.h>
#include <linux/cpu.h>
#include <linux/err.h>
#include <linux/genalloc.h>
@@ -52,6 +53,14 @@ static int am33xx_pm_suspend(suspend_state_t suspend_state)
{
int i, ret = 0;
+ /*
+ * For RTC only mode with DDR in selfresh we need to save
+ * clocks context at the very end
+ */
+ if (suspend_state == PM_SUSPEND_MEM &&
+ pm_ops->check_off_mode_enable())
+ clk_save_context();
+
ret = pm_ops->soc_suspend((unsigned long)suspend_state,
am33xx_do_wfi_sram);
@@ -77,6 +86,10 @@ static int am33xx_pm_suspend(suspend_state_t suspend_state)
}
}
+ if (suspend_state == PM_SUSPEND_MEM &&
+ pm_ops->check_off_mode_enable())
+ clk_restore_context();
+
return ret;
}
diff --git a/include/linux/platform_data/pm33xx.h b/include/linux/platform_data/pm33xx.h
index f9bed2a..36f7007 100644
--- a/include/linux/platform_data/pm33xx.h
+++ b/include/linux/platform_data/pm33xx.h
@@ -25,6 +25,7 @@ struct am33xx_pm_platform_data {
int (*init)(void);
int (*soc_suspend)(unsigned int state, int (*fn)(unsigned long));
struct am33xx_pm_sram_addr *(*get_sram_addrs)(void);
+ int (*check_off_mode_enable)(void);
};
struct am33xx_pm_sram_data {
--
1.9.1
next prev parent reply other threads:[~2018-06-21 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 8:15 [PATCH v3 0/4] clk: clk: Add functions to save/restore clock context en-masse Keerthy
2018-06-21 8:15 ` [PATCH v3 1/4] " Keerthy
2018-06-21 8:15 ` [PATCH v3 2/4] clk: clk: Add clk_gate_restore_context function Keerthy
2018-06-21 8:15 ` [PATCH v3 3/4] clk: ti: Add functions to save/restore clk context Keerthy
2018-06-21 8:15 ` Keerthy [this message]
2018-07-10 5:56 ` [PATCH v3 0/4] clk: clk: Add functions to save/restore clock context en-masse Tony Lindgren
2018-08-13 15:25 ` Tero Kristo
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=1529568907-19930-5-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=d-gerlach@ti.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).