From: "Jonas Bonn" <jonas.bonn@gmail.com>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] API for system clocks (oscillators)
Date: Thu, 30 Oct 2008 17:27:30 +0100 [thread overview]
Message-ID: <7a6abd110810300927l428b11f3u509ad31364c08f1f@mail.gmail.com> (raw)
In-Reply-To: <9e4733910810300840v7cd45c2cu629d23a27a02c61a@mail.gmail.com>
>
> 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...
/Jonas
next prev parent reply other threads:[~2008-10-30 16:27 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 [this message]
2008-10-30 16:39 ` Jon Smirl
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:
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=7a6abd110810300927l428b11f3u509ad31364c08f1f@mail.gmail.com \
--to=jonas.bonn@gmail.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®