From: Michael Turquette <mturquette@linaro.org>
To: Dong Aisheng <aisheng.dong@freescale.com>, linux-clk@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, sboyd@codeaurora.org,
shawn.guo@linaro.org, b29396@freescale.com,
linux-arm-kernel@lists.infradead.org,
Ranjani.Vaidyanathan@freescale.com, b20596@freescale.com,
r64343@freescale.com, b20788@freescale.com
Subject: Re: [PATCH v2 1/5] clk: remove duplicated code with __clk_set_parent_after
Date: Wed, 27 May 2015 21:09:19 -0700 [thread overview]
Message-ID: <20150528040919.22384.79189@quantum> (raw)
In-Reply-To: <1431610143-21853-2-git-send-email-aisheng.dong@freescale.com>
Quoting Dong Aisheng (2015-05-14 06:28:59)
> __clk_set_parent_after() actually used the second argument then we
> could put this duplicate logic in there and call it with a different
> order of arguments in the success vs. error paths in this function.
> =
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Suggested-by: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Dong Aisheng <aisheng.dong@freescale.com>
Patch looks good to me.
Also just noticed that the second argument to __clk_set_parent_after is
never used :-(
Regards,
Mike
> ---
> drivers/clk/clk.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
> =
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index 659f2b0..0e813ea 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -1159,14 +1159,8 @@ static int __clk_set_parent(struct clk_core *core,=
struct clk_core *parent,
> flags =3D clk_enable_lock();
> clk_reparent(core, old_parent);
> clk_enable_unlock(flags);
> + __clk_set_parent_after(core, old_parent, parent);
> =
> - if (core->prepare_count) {
> - flags =3D clk_enable_lock();
> - clk_core_disable(core);
> - clk_core_disable(parent);
> - clk_enable_unlock(flags);
> - clk_core_unprepare(parent);
> - }
> return ret;
> }
> =
> -- =
> 1.9.1
>=20
WARNING: multiple messages have this Message-ID (diff)
From: mturquette@linaro.org (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] clk: remove duplicated code with __clk_set_parent_after
Date: Wed, 27 May 2015 21:09:19 -0700 [thread overview]
Message-ID: <20150528040919.22384.79189@quantum> (raw)
In-Reply-To: <1431610143-21853-2-git-send-email-aisheng.dong@freescale.com>
Quoting Dong Aisheng (2015-05-14 06:28:59)
> __clk_set_parent_after() actually used the second argument then we
> could put this duplicate logic in there and call it with a different
> order of arguments in the success vs. error paths in this function.
>
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Suggested-by: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Dong Aisheng <aisheng.dong@freescale.com>
Patch looks good to me.
Also just noticed that the second argument to __clk_set_parent_after is
never used :-(
Regards,
Mike
> ---
> drivers/clk/clk.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index 659f2b0..0e813ea 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -1159,14 +1159,8 @@ static int __clk_set_parent(struct clk_core *core, struct clk_core *parent,
> flags = clk_enable_lock();
> clk_reparent(core, old_parent);
> clk_enable_unlock(flags);
> + __clk_set_parent_after(core, old_parent, parent);
>
> - if (core->prepare_count) {
> - flags = clk_enable_lock();
> - clk_core_disable(core);
> - clk_core_disable(parent);
> - clk_enable_unlock(flags);
> - clk_core_unprepare(parent);
> - }
> return ret;
> }
>
> --
> 1.9.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Michael Turquette <mturquette@linaro.org>
To: Dong Aisheng <aisheng.dong@freescale.com>, linux-clk@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, sboyd@codeaurora.org,
shawn.guo@linaro.org, b29396@freescale.com,
linux-arm-kernel@lists.infradead.org,
Ranjani.Vaidyanathan@freescale.com, b20596@freescale.com,
r64343@freescale.com, b20788@freescale.com
Subject: Re: [PATCH v2 1/5] clk: remove duplicated code with __clk_set_parent_after
Date: Wed, 27 May 2015 21:09:19 -0700 [thread overview]
Message-ID: <20150528040919.22384.79189@quantum> (raw)
In-Reply-To: <1431610143-21853-2-git-send-email-aisheng.dong@freescale.com>
Quoting Dong Aisheng (2015-05-14 06:28:59)
> __clk_set_parent_after() actually used the second argument then we
> could put this duplicate logic in there and call it with a different
> order of arguments in the success vs. error paths in this function.
>
> Cc: Mike Turquette <mturquette@linaro.org>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Suggested-by: Stephen Boyd <sboyd@codeaurora.org>
> Signed-off-by: Dong Aisheng <aisheng.dong@freescale.com>
Patch looks good to me.
Also just noticed that the second argument to __clk_set_parent_after is
never used :-(
Regards,
Mike
> ---
> drivers/clk/clk.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index 659f2b0..0e813ea 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -1159,14 +1159,8 @@ static int __clk_set_parent(struct clk_core *core, struct clk_core *parent,
> flags = clk_enable_lock();
> clk_reparent(core, old_parent);
> clk_enable_unlock(flags);
> + __clk_set_parent_after(core, old_parent, parent);
>
> - if (core->prepare_count) {
> - flags = clk_enable_lock();
> - clk_core_disable(core);
> - clk_core_disable(parent);
> - clk_enable_unlock(flags);
> - clk_core_unprepare(parent);
> - }
> return ret;
> }
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2015-05-28 4:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 13:28 [PATCH v2 0/5] clk: support clocks which requires parent clock on during operation Dong Aisheng
2015-05-14 13:28 ` Dong Aisheng
2015-05-14 13:28 ` [PATCH v2 1/5] clk: remove duplicated code with __clk_set_parent_after Dong Aisheng
2015-05-14 13:28 ` Dong Aisheng
2015-05-28 4:09 ` Michael Turquette [this message]
2015-05-28 4:09 ` Michael Turquette
2015-05-28 4:09 ` Michael Turquette
2015-05-28 8:25 ` Dong Aisheng
2015-05-28 8:25 ` Dong Aisheng
2015-07-15 12:25 ` Dong Aisheng
2015-07-15 12:25 ` Dong Aisheng
2015-07-15 12:25 ` Dong Aisheng
2015-07-15 12:29 ` Dong Aisheng
2015-07-15 12:29 ` Dong Aisheng
2015-07-15 12:29 ` Dong Aisheng
2015-07-22 14:08 ` Dong Aisheng
2015-07-22 14:08 ` Dong Aisheng
2015-07-24 0:11 ` Michael Turquette
2015-07-24 0:11 ` Michael Turquette
2015-07-24 3:23 ` Dong Aisheng
2015-07-24 3:23 ` Dong Aisheng
2015-05-14 13:29 ` [PATCH v2 2/5] clk: introduce clk_core_enable_lock and clk_core_disable_lock functions Dong Aisheng
2015-05-14 13:29 ` Dong Aisheng
2015-05-14 13:29 ` [PATCH v2 3/5] clk: move clk_disable_unused after clk_core_disable_unprepare function Dong Aisheng
2015-05-14 13:29 ` Dong Aisheng
2015-05-14 13:29 ` [PATCH v2 4/5] clk: core: add CLK_OPS_PARENT_ON flags to support clocks require parent on Dong Aisheng
2015-05-14 13:29 ` Dong Aisheng
2015-05-14 13:29 ` [PATCH v2 5/5] " Dong Aisheng
2015-05-14 13:29 ` Dong Aisheng
2015-05-20 11:42 ` [PATCH v2 0/5] clk: support clocks which requires parent clock on during operation Dong Aisheng
2015-05-20 11:42 ` 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=20150528040919.22384.79189@quantum \
--to=mturquette@linaro.org \
--cc=Ranjani.Vaidyanathan@freescale.com \
--cc=aisheng.dong@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=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 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.