All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saravana Kannan <skannan@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
	linux-arm-kernel@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-msm@vger.kernel.org,
	David Brownell <david-b@pacbell.net>
Subject: Re: Meaning of clk_round_rate()?
Date: Wed, 14 Jul 2010 23:27:16 -0700	[thread overview]
Message-ID: <4C3EAA44.7040607@codeaurora.org> (raw)
In-Reply-To: <20100714200324.GA18138@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> On Wed, Jul 14, 2010 at 11:05:46AM -0700, Stephen Boyd 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.

Fair enough explanation for clk_round_rate(). I guess I should take it 
as "it's up to the specific clock implementation on what it wants to do".

But what about the problem of a clock consumer trying to find a suitable 
frequency amongst the ones provided by a particular clock?

What are your thoughts on adding the following two APIs to linux/clk.h?
clk_round_rate_down/floor()
clk_round_rate_up/ceil()

Thanks,
Saravana

-- 
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: skannan@codeaurora.org (Saravana Kannan)
To: linux-arm-kernel@lists.infradead.org
Subject: Meaning of clk_round_rate()?
Date: Wed, 14 Jul 2010 23:27:16 -0700	[thread overview]
Message-ID: <4C3EAA44.7040607@codeaurora.org> (raw)
In-Reply-To: <20100714200324.GA18138@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> On Wed, Jul 14, 2010 at 11:05:46AM -0700, Stephen Boyd 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.

Fair enough explanation for clk_round_rate(). I guess I should take it 
as "it's up to the specific clock implementation on what it wants to do".

But what about the problem of a clock consumer trying to find a suitable 
frequency amongst the ones provided by a particular clock?

What are your thoughts on adding the following two APIs to linux/clk.h?
clk_round_rate_down/floor()
clk_round_rate_up/ceil()

Thanks,
Saravana

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  parent reply	other threads:[~2010-07-15  6:27 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
2010-07-15  3:37     ` Stephen Boyd
2010-07-15  6:27   ` Saravana Kannan [this message]
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=4C3EAA44.7040607@codeaurora.org \
    --to=skannan@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=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.