From: Stephen Boyd <sboyd@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Saravana Kannan <skannan@codeaurora.org>,
David Brownell <david-b@pacbell.net>
Subject: Re: Meaning of clk_round_rate()?
Date: Wed, 14 Jul 2010 20:37:05 -0700 [thread overview]
Message-ID: <4C3E8261.60307@codeaurora.org> (raw)
In-Reply-To: <20100714200324.GA18138@n2100.arm.linux.org.uk>
On 07/14/2010 01:03 PM, Russell King - ARM Linux wrote:
> clk_round_rate() returns the clock rate which will be set if you ask
> clk_set_rate() to set that rate. It provides a way to query from
> the implementation exactly what rate you'll get if you use clk_set_rate()
> with that same argument.
>
> So essentially, clk_set_rate() should be:
>
> static int clk_set_rate(struct clk *clk, unsigned long rate)
> {
> rate = clk_round_rate(clk, rate);
> return set_actual_rate(clk, rate);
> }
From what I understand, you're saying clk_round_rate() is defined as
what clk_set_rate() would do, which is call clk_round_rate() and then
set the rate with whatever is returned by clk_round_rate()? Isn't that a
recursive definition?
I'll play along though. The use of the function is to determine what the
rate will be if I call clk_set_rate(), but what is the implementation of
it suppose to be. I guess now I'm asking what should clk_set_rate() do?
Round up, down, to the closest value, or just fail if it's not exact.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: Meaning of clk_round_rate()?
Date: Wed, 14 Jul 2010 20:37:05 -0700 [thread overview]
Message-ID: <4C3E8261.60307@codeaurora.org> (raw)
In-Reply-To: <20100714200324.GA18138@n2100.arm.linux.org.uk>
On 07/14/2010 01:03 PM, Russell King - ARM Linux wrote:
> clk_round_rate() returns the clock rate which will be set if you ask
> clk_set_rate() to set that rate. It provides a way to query from
> the implementation exactly what rate you'll get if you use clk_set_rate()
> with that same argument.
>
> So essentially, clk_set_rate() should be:
>
> static int clk_set_rate(struct clk *clk, unsigned long rate)
> {
> rate = clk_round_rate(clk, rate);
> return set_actual_rate(clk, rate);
> }
From what I understand, you're saying clk_round_rate() is defined as
what clk_set_rate() would do, which is call clk_round_rate() and then
set the rate with whatever is returned by clk_round_rate()? Isn't that a
recursive definition?
I'll play along though. The use of the function is to determine what the
rate will be if I call clk_set_rate(), but what is the implementation of
it suppose to be. I guess now I'm asking what should clk_set_rate() do?
Round up, down, to the closest value, or just fail if it's not exact.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-07-15 3:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 18:05 Meaning of clk_round_rate()? Stephen Boyd
2010-07-14 18:05 ` Stephen Boyd
2010-07-14 20:03 ` Russell King - ARM Linux
2010-07-14 20:03 ` Russell King - ARM Linux
2010-07-15 3:37 ` Stephen Boyd [this message]
2010-07-15 3:37 ` Stephen Boyd
2010-07-15 6:27 ` Saravana Kannan
2010-07-15 6:27 ` Saravana Kannan
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=4C3E8261.60307@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=david-b@pacbell.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=skannan@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.