From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: rockchip: set correct stabilization thresholds in suspend
Date: Sat, 25 Jul 2015 01:09:23 +0200 [thread overview]
Message-ID: <1460722.2xOTZfOB49@diego> (raw)
In-Reply-To: <4610448.RXXf22Qoxl@diego>
Hi Chris,
Am Donnerstag, 23. Juli 2015, 10:29:34 schrieb Heiko St?bner:
> diff --git a/arch/arm/mach-rockchip/pm.c b/arch/arm/mach-rockchip/pm.c
> index 892bace..04d3028 100644
> --- a/arch/arm/mach-rockchip/pm.c
> +++ b/arch/arm/mach-rockchip/pm.c
> @@ -145,6 +145,10 @@ static void rk3288_slp_mode_set(int level)
>
> mode_set1 |= BIT(PMU_CLR_ALIVE) | BIT(PMU_CLR_BUS) |
> BIT(PMU_CLR_PERI) | BIT(PMU_CLR_DMA);
> +
> + /* 30ms on a 32kHz clock for osc and pmic stabilization */
> + regmap_write(pmu_regmap, RK3288_PMU_OSC_CNT, 32 * 30);
> + regmap_write(pmu_regmap, RK3288_PMU_STABL_CNT, 32 * 30);
The deep suspend mode has two bits handling the 32kHz clock switch (PMU_USE_LF
and ALIVE_USE_LF). Just for my understanding, are these always supposed to be
set to the same value or can there be a case when only one of them is set?
Also when deciding the correct stabilization delays on which of the two are
these dependant?
I.e. something like
stabl_cnt = PMU_PMU_USE_LF ? 32 : 24000
osc_cnt = PMU_ALIVE_USE_LF ? 32 : 24000
or are these always to be set similarly?
Thanks
Heiko
next prev parent reply other threads:[~2015-07-24 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 8:29 [PATCH v2 1/2] ARM: rockchip: set correct stabilization thresholds in suspend Heiko Stübner
2015-07-23 8:30 ` [PATCH v2 2/2] ARM: rockchip: enable PMU_GPIOINT_WAKEUP_EN when entering shallow suspend Heiko Stübner
2015-07-24 23:09 ` Heiko Stübner [this message]
2015-07-31 2:57 ` [PATCH v2 1/2] ARM: rockchip: set correct stabilization thresholds in suspend Chris Zhong
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=1460722.2xOTZfOB49@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).