All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Sachin Kamat <sachin.kamat@linaro.org>,
	Andrew Bresticker <abrestic@chromium.org>,
	t.figa@samsung.com, linux-samsung-soc@vger.kernel.org,
	mturquette@linaro.org
Subject: Re: [PATCH 1/3] clk: exynos5250: save/restore EPLL0 configuration
Date: Sun, 10 Nov 2013 18:01:28 +0100	[thread overview]
Message-ID: <2334797.Ti06tGyoel@flatron> (raw)
In-Reply-To: <1383905648-23733-1-git-send-email-sachin.kamat@linaro.org>

Hi Sachin, Andrew,

On Friday 08 of November 2013 15:44:06 Sachin Kamat wrote:
> From: Andrew Bresticker <abrestic@chromium.org>
> 
> The EPLL configuration register needs to be saved across
> suspend/resume.
> 
> Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> ---
>  drivers/clk/samsung/clk-exynos5250.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/clk/samsung/clk-exynos5250.c b/drivers/clk/samsung/clk-exynos5250.c
> index ee866e377c80..6767635dc895 100644
> --- a/drivers/clk/samsung/clk-exynos5250.c
> +++ b/drivers/clk/samsung/clk-exynos5250.c
> @@ -143,6 +143,7 @@ static unsigned long exynos5250_clk_regs[] __initdata = {
>  	SRC_CPU,
>  	DIV_CPU0,
>  	SRC_CORE1,
> +	EPLL_CON0,

What about EPLL_CON1 and EPLL_CON2? Also, have you considered register
restoration order?

Anyway, I believe it's not the correct way to restore PLL configuration.
See my Samsung PM consolidation series, especially patch [1] to see my
proposed way of handling this. (Beware of a bug that snuck into this patch
 - samsung_clk_save() is not being called for PLL registers.)

[1] http://thread.gmane.org/gmane.linux.kernel.samsung-soc/24078/focus=24087

Best regards,
Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] clk: exynos5250: save/restore EPLL0 configuration
Date: Sun, 10 Nov 2013 18:01:28 +0100	[thread overview]
Message-ID: <2334797.Ti06tGyoel@flatron> (raw)
In-Reply-To: <1383905648-23733-1-git-send-email-sachin.kamat@linaro.org>

Hi Sachin, Andrew,

On Friday 08 of November 2013 15:44:06 Sachin Kamat wrote:
> From: Andrew Bresticker <abrestic@chromium.org>
> 
> The EPLL configuration register needs to be saved across
> suspend/resume.
> 
> Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> ---
>  drivers/clk/samsung/clk-exynos5250.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/clk/samsung/clk-exynos5250.c b/drivers/clk/samsung/clk-exynos5250.c
> index ee866e377c80..6767635dc895 100644
> --- a/drivers/clk/samsung/clk-exynos5250.c
> +++ b/drivers/clk/samsung/clk-exynos5250.c
> @@ -143,6 +143,7 @@ static unsigned long exynos5250_clk_regs[] __initdata = {
>  	SRC_CPU,
>  	DIV_CPU0,
>  	SRC_CORE1,
> +	EPLL_CON0,

What about EPLL_CON1 and EPLL_CON2? Also, have you considered register
restoration order?

Anyway, I believe it's not the correct way to restore PLL configuration.
See my Samsung PM consolidation series, especially patch [1] to see my
proposed way of handling this. (Beware of a bug that snuck into this patch
 - samsung_clk_save() is not being called for PLL registers.)

[1] http://thread.gmane.org/gmane.linux.kernel.samsung-soc/24078/focus=24087

Best regards,
Tomasz

  parent reply	other threads:[~2013-11-10 17:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 10:14 [PATCH 1/3] clk: exynos5250: save/restore EPLL0 configuration Sachin Kamat
2013-11-08 10:14 ` Sachin Kamat
2013-11-08 10:14 ` [PATCH 2/3] clk: exynos5250: fix sysmmu_mfc{l,r} gate clocks Sachin Kamat
2013-11-08 10:14   ` Sachin Kamat
2013-11-10 17:08   ` Tomasz Figa
2013-11-10 17:08     ` Tomasz Figa
2013-11-11  3:11     ` Sachin Kamat
2013-11-11  3:11       ` Sachin Kamat
2013-12-18 18:09     ` Sachin Kamat
2013-12-18 18:09       ` Sachin Kamat
2013-12-18 18:28       ` Tomasz Figa
2013-12-18 18:28         ` Tomasz Figa
2013-12-18 19:24         ` Mike Turquette
2013-12-18 19:24           ` Mike Turquette
2013-12-19  0:36           ` Tomasz Figa
2013-12-19  0:36             ` Tomasz Figa
2013-12-19 14:10       ` Tomasz Figa
2013-12-19 14:10         ` Tomasz Figa
2013-12-19 15:35         ` Sachin Kamat
2013-12-19 15:35           ` Sachin Kamat
2013-12-20 21:14           ` Tomasz Figa
2013-12-21  4:07             ` Sachin Kamat
2013-12-30 17:52               ` Tomasz Figa
2013-12-31  2:51                 ` Sachin Kamat
2013-11-08 10:14 ` [PATCH 3/3] clk: exynos5250: register APLL rate table Sachin Kamat
2013-11-08 10:14   ` Sachin Kamat
2013-11-10 17:14   ` Tomasz Figa
2013-11-10 17:14     ` Tomasz Figa
2013-12-19  3:44     ` Sachin Kamat
2013-12-19  3:44       ` Sachin Kamat
2013-12-31  3:16       ` Sachin Kamat
2013-12-31  3:16         ` Sachin Kamat
2014-01-02 15:22         ` Tomasz Figa
2014-01-02 15:22           ` Tomasz Figa
2013-11-08 10:21 ` [PATCH 1/3] clk: exynos5250: save/restore EPLL0 configuration Sachin Kamat
2013-11-08 10:21   ` Sachin Kamat
2013-11-10 17:01 ` Tomasz Figa [this message]
2013-11-10 17:01   ` Tomasz Figa

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=2334797.Ti06tGyoel@flatron \
    --to=tomasz.figa@gmail.com \
    --cc=abrestic@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=sachin.kamat@linaro.org \
    --cc=t.figa@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.