Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Tomasz Figa <t.figa@samsung.com>
To: Shaik Ameer Basha <shaik.ameer@samsung.com>,
	linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org
Cc: kgene.kim@samsung.com, tomasz.figa@gmail.com,
	mark.rutland@arm.com, pawel.moll@arm.com, swarren@wwwdotorg.org,
	prathyush.k@samsung.com, abrestic@chromium.org,
	arunkk.samsung@gmail.com, joshi@samsung.com,
	Arun Kumar K <arun.kk@samsung.com>
Subject: Re: [PATCH v2 1/3] ARM: EXYNOS: Add support for clock handling in power domain
Date: Tue, 10 Jun 2014 17:38:16 +0200	[thread overview]
Message-ID: <53972668.7090903@samsung.com> (raw)
In-Reply-To: <1401105384-8678-2-git-send-email-shaik.ameer@samsung.com>

Hi,

On 26.05.2014 13:56, Shaik Ameer Basha wrote:
> From: Prathyush K <prathyush.k@samsung.com>
> 
> While powering on/off a local powerdomain in exynos5 chipsets, the input
> clocks to each device gets modified. This behaviour is based on the
> SYSCLK_SYS_PWR_REG registers.
> E.g. SYSCLK_MFC_SYS_PWR_REG = 0x0, the parent of input clock to MFC
> 				   (aclk333) gets modified to oscclk
> 			    = 0x1, no change in clocks.
> The recommended value of SYSCLK_SYS_PWR_REG before power gating any
> domain is 0x0. So we must also restore the clocks while powering on a
> domain everytime.
> 
> This patch adds the framework for getting the required mux and parent clocks
> through a power domain device node. With this patch, while powering off
> a domain, parent is set to oscclk and while powering back on, its re-set
> to the correct parent which is as per the recommended pd on/off
> sequence.
> 
> Signed-off-by: Prathyush K <prathyush.k@samsung.com>
> Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
> Signed-off-by: Arun Kumar K <arun.kk@samsung.com>
> Signed-off-by: Shaik Ameer Basha <shaik.ameer@samsung.com>
> ---
>  .../bindings/arm/exynos/power_domain.txt           |   20 +++++++
>  arch/arm/mach-exynos/pm_domains.c                  |   59 +++++++++++++++++++-
>  2 files changed, 78 insertions(+), 1 deletion(-)
> 

Reviewed-by: Tomasz Figa <t.figa@samsung.com>

--
Best regards,
Tomasz

  parent reply	other threads:[~2014-06-10 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 11:56 [PATCH v2 0/3] Power-domain clk handling Shaik Ameer Basha
2014-05-26 11:56 ` [PATCH v2 1/3] ARM: EXYNOS: Add support for clock handling in power domain Shaik Ameer Basha
2014-05-29  9:41   ` Arun Kumar K
2014-06-10 15:38   ` Tomasz Figa [this message]
     [not found] ` <1401105384-8678-1-git-send-email-shaik.ameer-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-05-26 11:56   ` [PATCH v2 2/3] clk: exynos5420: Add IDs for clocks used in PD mfc Shaik Ameer Basha
2014-06-10 15:39     ` Tomasz Figa
2014-06-25 11:36       ` Tomasz Figa
2014-05-26 11:56 ` [PATCH v2 3/3] ARM: dts: Add clock property for mfc_pd in 5420 Shaik Ameer Basha

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=53972668.7090903@samsung.com \
    --to=t.figa@samsung.com \
    --cc=abrestic@chromium.org \
    --cc=arun.kk@samsung.com \
    --cc=arunkk.samsung@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=joshi@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=prathyush.k@samsung.com \
    --cc=shaik.ameer@samsung.com \
    --cc=swarren@wwwdotorg.org \
    --cc=tomasz.figa@gmail.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