From: Dong Aisheng <aisheng.dong@freescale.com>
To: Dong Aisheng <b29396@freescale.com>
Cc: <linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sboyd@codeaurora.org>, <mturquette@baylibre.com>,
<shawnguo@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<Ranjani.Vaidyanathan@freescale.com>, <b20596@freescale.com>,
<r64343@freescale.com>, <b20788@freescale.com>
Subject: Re: [PATCH V3 0/5] clk: support clocks which requires parent clock on during operation
Date: Tue, 4 Aug 2015 17:45:57 +0800 [thread overview]
Message-ID: <20150804094556.GE24870@shlinux1.ap.freescale.net> (raw)
In-Reply-To: <20150728143824.GB16916@shlinux1.ap.freescale.net>
On Tue, Jul 28, 2015 at 10:38:25PM +0800, Dong Aisheng wrote:
> On Tue, Jul 28, 2015 at 09:19:40PM +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.
> >
> > 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
> >
> > Change Log:
> > v2->v3:
> > * rebased version, no other changes.
> >
> > v1->v2:
> > Mainly addressed Stephen Boyd's comments
> > * remove dupliciated code with __clk_set_parent_after
> > * introduce more clk_core_x APIs for core easily use
> > * move clk_disable_unused code position
> > * use clk_core_x API to make code more clean and easily read
> >
> > Dong Aisheng (5):
> > clk: remove duplicated code with __clk_set_parent_after
> > clk: introduce clk_core_enable_lock and clk_core_disable_lock
> > functions
> > clk: move clk_disable_unused after clk_core_disable_unprepare function
> > clk: core: add CLK_OPS_PARENT_ON flags to support clocks require
> > parent on
> > clk: core: add CLK_OPS_PARENT_ON flags to support clocks require
> > parent on
> >
> > drivers/clk/clk.c | 338 +++++++++++++++++++++++++------------------
> > include/linux/clk-provider.h | 5 +
> > 2 files changed, 200 insertions(+), 143 deletions(-)
> >
>
> Sorry, forgot to update Mike's new email address.
> Updated.
>
Ping...
Regards
Dong Aisheng
> Regards
> Dong Aisheng
>
> > --
> > 1.9.1
> >
next prev parent reply other threads:[~2015-08-04 9:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 13:19 Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 1/5] clk: remove duplicated code with __clk_set_parent_after Dong Aisheng
2015-08-13 18:25 ` Stephen Boyd
2015-07-28 13:19 ` [PATCH V3 2/5] clk: introduce clk_core_enable_lock and clk_core_disable_lock functions Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 3/5] clk: move clk_disable_unused after clk_core_disable_unprepare function Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 4/5] clk: core: add CLK_OPS_PARENT_ON flags to support clocks require parent on Dong Aisheng
2015-08-14 1:01 ` Stephen Boyd
2015-08-17 12:45 ` Dong Aisheng
2015-08-19 11:07 ` Dong Aisheng
2015-09-09 9:20 ` Dong Aisheng
2015-07-28 13:19 ` [PATCH V3 5/5] " Dong Aisheng
2015-07-28 14:38 ` [PATCH V3 0/5] clk: support clocks which requires parent clock on during operation Dong Aisheng
2015-08-04 9:45 ` Dong Aisheng [this message]
2015-08-13 10:17 ` Dong Aisheng
2016-02-22 14:55 ` Fabio Estevam
2016-02-23 3:45 ` Dong Aisheng
2015-08-13 20:55 ` Joachim Eastwood
2016-03-30 16:00 ` Fabio Estevam
2016-03-31 13:51 ` 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=20150804094556.GE24870@shlinux1.ap.freescale.net \
--to=aisheng.dong@freescale.com \
--cc=Ranjani.Vaidyanathan@freescale.com \
--cc=b20596@freescale.com \
--cc=b20788@freescale.com \
--cc=b29396@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=r64343@freescale.com \
--cc=sboyd@codeaurora.org \
--cc=shawnguo@kernel.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