From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: remove .init from sh7709_cpu_clk_ops
Date: Mon, 14 Sep 2009 02:00:28 +0000 [thread overview]
Message-ID: <20090914020027.GC15078@linux-sh.org> (raw)
In-Reply-To: <20090914004851.GA14697@rafazurita.homelinux.net>
On Sun, Sep 13, 2009 at 09:48:51PM -0300, Rafael Ignacio Zurita wrote:
> It avoids to change the parent of sh7709_cpu_clk. With this change
> master_clk is the parent of cpu_clk (from clk_cpg_legacy), and it
> prevents the second mutex_lock(&clock_list_sem) while the first
> one is still locked.
>
> Signed-off-by: Rafael Ignacio Zurita <rizurita@yahoo.com>
> ---
> arch/sh/kernel/cpu/sh3/clock-sh7709.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/arch/sh/kernel/cpu/sh3/clock-sh7709.c b/arch/sh/kernel/cpu/sh3/clock-sh7709.c
> index fa30b60..f3064f9 100644
> --- a/arch/sh/kernel/cpu/sh3/clock-sh7709.c
> +++ b/arch/sh/kernel/cpu/sh3/clock-sh7709.c
> @@ -78,7 +78,6 @@ static unsigned long cpu_clk_recalc(struct clk *clk)
> }
>
> static struct clk_ops sh7709_cpu_clk_ops = {
> - .init = set_bus_parent,
> .recalc = cpu_clk_recalc,
> };
>
There is basically no way for this set_bus_parent() code to work at all
in the current scheme, so you are better off killing it off entirely. The
other case (which is currently protected by an unused ifdef) isn't going
to work either.
I'll check this in with the rest of it killed off, though ideally the
sh7709 clock framework wants to be rewritten given that it obviously does
not adhere to the legacy CPG layout very well in the first place.
prev parent reply other threads:[~2009-09-14 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 0:48 [PATCH] sh: remove .init from sh7709_cpu_clk_ops Rafael Ignacio Zurita
2009-09-14 2:00 ` Paul Mundt [this message]
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=20090914020027.GC15078@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.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 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.