From: Mark Brown <broonie@sirena.org.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 20:08:54 +0000 [thread overview]
Message-ID: <20081030200851.GC13678@sirena.org.uk> (raw)
In-Reply-To: <7a6abd110810300741wf73f838laa3754e23c22baf3@mail.gmail.com>
On Thu, Oct 30, 2008 at 03:41:17PM +0100, 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
Something like this would certainly be very useful for audio clocking if
it could be made to fit - that can get complex, is partly off-SoC and
frequently has multiple interrelated clock sources available, often with
various hard to describe interdependencies with constraints coming from
multiple sources and changing dynamically at run time.
In general your problem statement looks fairly sane. I've not reviewed
this in detail but do think you should have a look at the OMAP stuff.
One thing to watch out for is that you'll find clocks doing things like
originating in one chip, going through another and being fed back into
the original chip.
prev parent reply other threads:[~2008-10-30 20:17 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
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 [this message]
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=20081030200851.GC13678@sirena.org.uk \
--to=broonie@sirena.org.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®