From: Dan Malek <dan@embeddededge.com>
To: Bob Lees <bob@diamond.demon.co.uk>
Cc: linux-mips@linux-mips.org
Subject: Re: Frequency (cpu speed) control on AU1100
Date: Tue, 30 Mar 2004 16:56:19 -0500 [thread overview]
Message-ID: <4069ED03.8060202@embeddededge.com> (raw)
In-Reply-To: 200403302137.38123.bob@diamond.demon.co.uk
Bob Lees wrote:
> ....I suspect I am
> missing something somewhere, but I can't find any references to cpu speed
> control for the MIPS processors, specically the au1x range.
The Au1xxx has a PLL that multiplies the incoming 12 MHz clock up to the
internal frequency. Just be aware there are lots of peripheral clocks
and bus clocks derived from this internal frequency. There is code
in the kernel power management to allow changing the frequency during
operation of Linux, but I don't know how well it works today as I have
not tested that for quite some time.
Thanks.
-- Dan
next prev parent reply other threads:[~2004-03-30 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 20:37 Frequency (cpu speed) control on AU1100 Bob Lees
2004-03-30 21:14 ` Pete Popov
2004-03-30 21:56 ` Dan Malek [this message]
2004-03-30 22:38 ` Bob Lees
2004-03-30 22:48 ` Pete Popov
2004-03-31 14:33 ` Bob Lees
2004-03-30 23:26 ` Dan Malek
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=4069ED03.8060202@embeddededge.com \
--to=dan@embeddededge.com \
--cc=bob@diamond.demon.co.uk \
--cc=linux-mips@linux-mips.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