From: Alan Jenkins <aj504@student.cs.york.ac.uk>
To: Jonas Bonn <jonas.bonn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] API for system clocks (oscillators)
Date: Thu, 30 Oct 2008 15:31:07 +0000 [thread overview]
Message-ID: <4909D33B.4050108@tuffmail.co.uk> (raw)
In-Reply-To: <7a6abd110810300741wf73f838laa3754e23c22baf3@mail.gmail.com>
Jonas Bonn wrote:
> I'd be happy to get some feedback on this, whether or not it is a good
> idea or even the right way to approach this problem. This is part of
> the puzzle for solving the problem of frequency scaling on (primarily)
> embedded systems where there are many clocks, (changeable)
> relationships between clocks, device dependencies on clock
> availability, and device constraints on frequency that appear and
> disappear as devices are enabled and disabled.
>
> This is a first draft (almost thinking-out-loud version), so please
> read it as such... there is much room for improvement and all
> suggestions are welcome. Release early, release often, right? Well,
> this is an "early" specification...
Hmm, how does this relate to the OMAP clock domain work? I read about
it on LWN and was impressed...
omap2-clock merge: <http://thread.gmane.org/gmane.linux.ports.arm.omap/9464>
Len's OLS notes: <http://lwn.net/Articles/292447/>
Regards
Alan
next prev parent reply other threads:[~2008-10-30 15:31 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 [this message]
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
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=4909D33B.4050108@tuffmail.co.uk \
--to=aj504@student.cs.york.ac.uk \
--cc=jonas.bonn@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®