From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Alex Frid <afrid@nvidia.com>
Subject: Re: [PATCH] clk: Add requested rate to clock summary output
Date: Fri, 7 Apr 2017 14:49:01 +0300 [thread overview]
Message-ID: <20170407114901.GA30730@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <1490188803-13034-1-git-send-email-pdeschrijver@nvidia.com>
On Wed, Mar 22, 2017 at 03:20:03PM +0200, Peter De Schrijver wrote:
> From: Alex Frid <afrid@nvidia.com>
>
> Added requested rate to clock summary output and to clock dump. This is
> useful for clock tree debugging. Also expand the clock name field in the
> clock tree debugfs output to provide room for deep multi-tier trees like
> on Tegra.
>
Ping! Any comments on this?
Peter.
> Signed-off-by: Alex Frid <afrid@nvidia.com>
> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> ---
> drivers/clk/clk.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index 0b815d1..3f6ae6d 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -2007,10 +2007,10 @@ static void clk_summary_show_one(struct seq_file *s, struct clk_core *c,
> if (!c)
> return;
>
> - seq_printf(s, "%*s%-*s %11d %12d %11lu %10lu %-3d\n",
> + seq_printf(s, "%*s%-*s %11d %12d %11lu %11lu %10lu %-3d\n",
> level * 3 + 1, "",
> - 30 - level * 3, c->name,
> - c->enable_count, c->prepare_count, clk_core_get_rate(c),
> + 48 - level * 3, c->name, c->enable_count,
> + c->prepare_count, clk_core_get_rate(c), c->req_rate,
> clk_core_get_accuracy(c), clk_core_get_phase(c));
> }
>
> @@ -2033,8 +2033,8 @@ static int clk_summary_show(struct seq_file *s, void *data)
> struct clk_core *c;
> struct hlist_head **lists = (struct hlist_head **)s->private;
>
> - seq_puts(s, " clock enable_cnt prepare_cnt rate accuracy phase\n");
> - seq_puts(s, "----------------------------------------------------------------------------------------\n");
> + seq_puts(s, " clock enable_cnt prepare_cnt rate req_rate accuracy phase\n");
> + seq_puts(s, "----------------------------------------------------------------------------------------------------------------------\n");
>
> clk_prepare_lock();
>
> @@ -2070,6 +2070,7 @@ static void clk_dump_one(struct seq_file *s, struct clk_core *c, int level)
> seq_printf(s, "\"enable_count\": %d,", c->enable_count);
> seq_printf(s, "\"prepare_count\": %d,", c->prepare_count);
> seq_printf(s, "\"rate\": %lu,", clk_core_get_rate(c));
> + seq_printf(s, "\"req_rate\": %lu,", c->req_rate);
> seq_printf(s, "\"accuracy\": %lu,", clk_core_get_accuracy(c));
> seq_printf(s, "\"phase\": %d", clk_core_get_phase(c));
> }
> --
> 1.9.1
>
next prev parent reply other threads:[~2017-04-07 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 13:20 [PATCH] clk: Add requested rate to clock summary output Peter De Schrijver
2017-04-07 11:49 ` Peter De Schrijver [this message]
2017-04-12 16:48 ` Stephen Boyd
2017-04-13 13:50 ` Peter De Schrijver
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=20170407114901.GA30730@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=afrid@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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.