From: "Leo L. Schwab" <ewhac@best.com>
To: linux-pm@lists.osdl.org
Subject: Re: Few enhancement ideas
Date: Thu, 14 Jul 2005 14:56:07 -0700 [thread overview]
Message-ID: <20050714215607.GA16613@best.com> (raw)
In-Reply-To: <1121277175.6338.105.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
On Wed, Jul 13, 2005 at 08:52:55PM +0300, Amit Kucheria wrote:
> The Nokia 770 Linux team has made many contributions to the Linux-OMAP
> port, some of the PM-specific ones being:
>
> - Dynamic tick patch by Tony Lindgren
> (http://www.muru.com/linux/dyntick/): Initially for
> the OMAP architecture followed by the recent x86 port
> - Clock framework for the OMAP architecture - Thanks to Tuukka Tikkanen
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> - PM-enabling various drivers in the mach-omap tree
>
My thanks to you and Tuukka Tikkanen as well. I took the ARM clock
API framework you developed for the OMAP, hacked it to shreds and got it
working on the Freescale i.MX1.
Some clocks on the i.MX1 are always running, so when they're unused,
I elected to spin them down the slowest available speed, saving a bit more
power. I also keep a copy of the requested target frequency so that when
parent clocks get changed, I can keep the child clocks running as close as
possible to the originally requested speed. This is useful for stuff like
the I2C bus and audio clocks, and really darned helpful in keeping the
console serial port working correctly.
When you were implementing the framework, did you have any thoughts
about where the initial clock frequencies "should" come from? It sounds
like a policy issue, and therefore compiling it into the kernel (as you've
done in your OMAP implementation) is The Wrong Thing. But it's not at all
clear where else it could go.
Again, my thanks. It was tons of help.
Schwab
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-07-14 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 17:52 Few enhancement ideas Amit Kucheria
2005-07-13 18:03 ` Jordan Crouse
2005-07-13 18:38 ` david-b
2005-07-15 13:04 ` Igor Stoppa
2005-07-14 21:56 ` Leo L. Schwab [this message]
2005-07-15 13:11 ` Igor Stoppa
2005-07-17 2:43 ` Pavel Machek
2005-07-17 16:52 ` Amit Kucheria
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=20050714215607.GA16613@best.com \
--to=ewhac@best.com \
--cc=linux-pm@lists.osdl.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