mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dong Aisheng <b29396@freescale.com>
To: Dong Aisheng <aisheng.dong@freescale.com>
Cc: <linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<sboyd@codeaurora.org>, <mturquette@linaro.org>,
	<shawn.guo@linaro.org>, <linux-arm-kernel@lists.infradead.org>,
	<Ranjani.Vaidyanathan@freescale.com>, <b20596@freescale.com>,
	<r64343@freescale.com>, <b20788@freescale.com>
Subject: Re: [PATCH RFC v1 0/5] clk: support clocks which requires parent clock on during operation
Date: Wed, 22 Apr 2015 14:12:43 +0800	[thread overview]
Message-ID: <20150422061240.GA25437@shlinux1.ap.freescale.net> (raw)
In-Reply-To: <1429107999-24413-1-git-send-email-aisheng.dong@freescale.com>

On Wed, Apr 15, 2015 at 10:26:34PM +0800, Dong Aisheng wrote:
> This patch series adds support in clock framework for clocks which operations
> requires its parent clock is on.
> 
> Such clock type is initially met on Freescale i.MX7D platform that all clocks
> operations, including enable/disable, rate change and re-parent, requires its
> parent clock on. No sure if any other SoC has the similar clock type.
> 
> Current clock core can not support such type of clock well.
> 
> This patch introduce a new flag CLK_SET_PARENT_ON to handle this special case
> in clock core that enable its parent clock firstly for each operation and disable
> it later after operation complete.
> 
> The most special case is for set_parent() operation which requires both parent,
> old one and new one, to be enabled at the same time during the operation.
> 
> Patch 1~3 are minor cleanup & fixes.
> Patch 4 add CLK_SET_PARENT_ON flags in clock core to support such type clocks
> Patch 5 show the need of introducing clk_core_enable_lock and
> 	clk_core_disable_lock to easily use and reduce duplicated code.
> 	It can be merged into patch 4 if required.
> 
> The patch series is based on for-next branch of Michael's git:
> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
> 
> Dong Aisheng (5):
>   clk: change clk_core name of __clk_set_parent_after
>   clk: add missing lock when call clk_core_enable in clk_set_parent
>   clk: remove unneeded __clk_enable and __clk_disable
>   clk: core: add CLK_SET_PARENT_ON flags to support clocks require
>     parent on
>   clk: introduce clk_core_enable_lock and clk_core_disable_lock
>     functions
> 

Gentle Ping.

Regards
Dong Aisheng

>  drivers/clk/clk.c            | 112 ++++++++++++++++++++++++++++++++++---------
>  include/linux/clk-provider.h |   5 ++
>  2 files changed, 94 insertions(+), 23 deletions(-)
> 
> -- 
> 1.9.1
> 

  parent reply	other threads:[~2015-04-22  6:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 14:26 Dong Aisheng
2015-04-15 14:26 ` [PATCH RFC v1 1/5] clk: change clk_core name of __clk_set_parent_after Dong Aisheng
2015-04-30 19:06   ` Stephen Boyd
2015-05-04  8:15     ` Dong Aisheng
2015-04-15 14:26 ` [PATCH RFC v1 2/5] clk: add missing lock when call clk_core_enable in clk_set_parent Dong Aisheng
2015-04-30 19:07   ` Stephen Boyd
2015-05-04  8:35     ` Dong Aisheng
2015-05-07  0:01       ` Stephen Boyd
2015-05-13  9:21         ` Dong Aisheng
2015-04-15 14:26 ` [PATCH RFC v1 3/5] clk: remove unneeded __clk_enable and __clk_disable Dong Aisheng
2015-04-30 19:09   ` Stephen Boyd
2015-04-30 22:05     ` Stephen Boyd
2015-05-04  8:16       ` Dong Aisheng
2015-04-15 14:26 ` [PATCH RFC v1 4/5] clk: core: add CLK_SET_PARENT_ON flags to support clocks require parent on Dong Aisheng
2015-05-01  1:09   ` Stephen Boyd
2015-05-04 10:36     ` Dong Aisheng
2015-05-06 23:34       ` Stephen Boyd
2015-05-13  9:20         ` Dong Aisheng
2015-04-15 14:26 ` [PATCH RFC v1 5/5] clk: introduce clk_core_enable_lock and clk_core_disable_lock functions Dong Aisheng
2015-05-01  1:10   ` Stephen Boyd
2015-05-04 10:38     ` Dong Aisheng
2015-04-22  6:12 ` Dong Aisheng [this message]
2015-04-30  2:37   ` [PATCH RFC v1 0/5] clk: support clocks which requires parent clock on during operation Dong Aisheng

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=20150422061240.GA25437@shlinux1.ap.freescale.net \
    --to=b29396@freescale.com \
    --cc=Ranjani.Vaidyanathan@freescale.com \
    --cc=aisheng.dong@freescale.com \
    --cc=b20596@freescale.com \
    --cc=b20788@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=r64343@freescale.com \
    --cc=sboyd@codeaurora.org \
    --cc=shawn.guo@linaro.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

Powered by JetHome