LKML Archive on
help / color / mirror / Atom feed
From: "Jon Smirl" <>
To: "Jonas Bonn" <>
Subject: Re: [RFC] API for system clocks (oscillators)
Date: Thu, 30 Oct 2008 12:39:42 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Oct 30, 2008 at 12:27 PM, Jonas Bonn <> wrote:
>> How does this compare to the framework in linux/include/linux/clk.h?
> clk.h is pretty much just an infrastructure for "storing" clock data
> and accessors... it does not provide:
> i) Constraints on selectable frequencies of active devices
> ii) Notifiers on frequency change, including changes due to events
> such as reparenting
> These are the big ones that cause headaches.  When I want to switch
> frequency, I have to check elsewhere which devices are active and
> which frequencies they allow.  When a frequency changes, I have to
> manually make sure that the active devices are notified properly of
> the change.  These are the main things that my document tries to
> consolidate into one framework.  Like I said, I'm not sure it's the
> right approach, that's why I requested feedback...

You could probably work those features into the existing clk framework.
clk_set_rate() could compute the constrains and return an error.
The API could be expanded with notifier support.

Jon Smirl

  reply	other threads:[~2008-10-30 16:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 14:41 Jonas Bonn
2008-10-30 15:31 ` Alan Jenkins
2008-10-30 16:19   ` Jonas Bonn
2008-10-30 15:40 ` Jon Smirl
2008-10-30 16:27   ` Jonas Bonn
2008-10-30 16:39     ` Jon Smirl [this message]
2008-10-30 16:40       ` Jon Smirl
2008-10-30 17:01       ` Jonas Bonn
2008-10-30 20:13         ` Mark Brown
2008-10-30 20:15           ` Jonas Bonn
2008-10-31 11:20             ` Mark Brown
2008-11-01 10:55               ` Jonas Bonn
2008-10-30 20:08 ` Mark Brown

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [RFC] API for system clocks (oscillators)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).