From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: Clock API and "maximum rate"
Date: Wed, 11 Jan 2012 16:58:44 +0000 [thread overview]
Message-ID: <20120111165844.GL3226@page> (raw)
In-Reply-To: <CAKGA1bmZGxxSfwGkpdyt7c-UYUTj+mV2AZhmhCUSEKTd12Q+4Q@mail.gmail.com>
Hi Matt,
On Wed, Jan 11, 2012 at 10:30:15AM -0600, Matt Sealey wrote:
> Just a curious question, is there any safe way in the current API or
> even by peeking a little behind the scenes to find out what the
> maximum clock rate would be for a given named clock or struct clk?
How about:
long max = clk_round_rate(clk, ~0LU);
clk_round_rate() is one of the optional API calls though.
Jamie
next prev parent reply other threads:[~2012-01-11 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 16:30 Clock API and "maximum rate" Matt Sealey
2012-01-11 16:58 ` Jamie Iles [this message]
2012-01-12 13:49 ` Matt Sealey
2012-01-12 14:11 ` Russell King - ARM Linux
2012-01-12 14:48 ` Matt Sealey
2012-01-12 18:37 ` Jamie Iles
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=20120111165844.GL3226@page \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@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 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.