From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vlad Zakharov" <Vladislav.Zakharov@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH] arc: get rate from clk driver instead of reading device tree
Date: Tue, 28 Feb 2017 15:11:03 +0000 [thread overview]
Message-ID: <1488294662.3913.11.camel@synopsys.com> (raw)
In-Reply-To: <d1db32ca-333e-e900-171e-3b0735cba2a2@synopsys.com>
Hi Vineet,
On Wed, 2017-02-22 at 10:34 -0800, Vineet Gupta wrote:
> On 02/22/2017 02:36 AM, Vlad Zakharov wrote:
> >
> > We were reading clock rate directly from device tree "clock-frequency"
> > property of corresponding clock node in show_cpuinfo function.
> >
> > Such approach is correct only in case cpu is always clocked by
> > "fixed-clock". If we use clock driver that allows rate to be changed
> > this won't work as rate may change during the time or even
> > "clock-frequency" property may not be presented at all.
> >
> > So this commit replaces reading device tree with getting rate from clock
> > driver. This approach is much more flexible and will work for both fixed
> > and mutable clocks.
> >
> > Signed-off-by: Vlad Zakharov <vzakhar@synopsys.com>
> > ---
> > arch/arc/kernel/setup.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/arc/kernel/setup.c b/arch/arc/kernel/setup.c
> > index 3093fa8..49b0804 100644
> > --- a/arch/arc/kernel/setup.c
> > +++ b/arch/arc/kernel/setup.c
> > @@ -10,6 +10,7 @@
> > #include <linux/fs.h>
> > #include <linux/delay.h>
> > #include <linux/root_dev.h>
> > +#include <linux/clk.h>
> > #include <linux/clk-provider.h>
> > #include <linux/clocksource.h>
> > #include <linux/console.h>
> > @@ -488,7 +489,8 @@ static int show_cpuinfo(struct seq_file *m, void *v)
> > {
> > char *str;
> > int cpu_id = ptr_to_cpu(v);
> > - struct device_node *core_clk = of_find_node_by_name(NULL, "core_clk");
> > + struct device *cpu_dev = get_cpu_device(cpu_id);
> > + struct clk *cpu_clk = clk_get(cpu_dev, "core_clk");
> > u32 freq = 0;
> >
> > if (!cpu_online(cpu_id)) {
> > @@ -502,7 +504,7 @@ static int show_cpuinfo(struct seq_file *m, void *v)
> >
> > seq_printf(m, arc_cpu_mumbojumbo(cpu_id, str, PAGE_SIZE));
> >
> > - of_property_read_u32(core_clk, "clock-frequency", &freq);
> > + freq = clk_get_rate(cpu_clk);
> > if (freq)
> > seq_printf(m, "CPU speed\t: %u.%02u Mhz\n",
> > freq / 1000000, (freq / 10000) % 100);
>
> I'm not too familiar with clk API, do u need to clk_put() afterwards ? @Alexey can
> u please check !
I'm not really sure why clk_put() got in the picture here at all.
As it is mentioned here http://elixir.free-electrons.com/source/include/linux/clk.h?v=4.10#L305
clk_put() means "free" the clock source.
Anyways this patch alone was not sufficient due to missing changes in .dts files and
Vlad is going to send v2 soonish.
-Alexey
next prev parent reply other threads:[~2017-02-28 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 10:36 Vlad Zakharov
2017-02-22 18:34 ` Vineet Gupta
2017-02-28 15:11 ` Alexey Brodkin [this message]
2017-02-22 18:49 ` Vineet Gupta
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=1488294662.3913.11.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=Vladislav.Zakharov@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.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