Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@embeddedalley.com>
To: Dominik Brodowski <linux@dominikbrodowski.de>,
	ralf@linux-mips.org, linux-mips@linux-mips.org
Cc: cpufreq@www.linux.org.uk
Subject: Re: CPU frequency scaling on MIPS (au1000/common/power.c)
Date: Fri, 24 Sep 2004 11:33:52 -0700 (PDT)	[thread overview]
Message-ID: <20040924183352.31414.qmail@web81407.mail.yahoo.com> (raw)
In-Reply-To: <20040923201916.38891.qmail@web81408.mail.yahoo.com>


AMD notified me that the frequency scaling will not be
supported moving forward and will not be guaranteed to
work. Therefore, I'll have to remove that code from
the kernel so that it's not misleading.

Pete

--- Pete Popov <ppopov@embeddedalley.com> wrote:

> 
> <snip>
> 
> > Therefore, I'd suggest that we update
> > arch/mips/au1000/common/power.c to
> > use the cpufreq infrastructure. 
> 
> 
> The current interface was written a few years ago
> for
> 2.4, when I couldn't find a general PM interface to
> start with.
> 
> 
> > Nonetheless I'd be willing to write
> > a "suggestion" on how to update
> > arch/mips/au1000/common/power.c, and
> > somebody with compiler and hardware could test it
> > then.
> 
> That would help, though I'm not sure when I would
> get
> to it personally. I'm working on 2.6 updates at the
> moment with some other developers, but PM is not on
> our list for now. If you're dying to work on it and
> hardware is the only issue, I might be able to help
> :)
> 
> > Are there other MIPS CPUs which support CPU
> > frequency scaling? 
> 
> Not that I know of, and not the way the Au1x
> supports
> it.
> 
> 
> Pete
> 
> 

  reply	other threads:[~2004-09-24 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 19:48 CPU frequency scaling on MIPS (au1000/common/power.c) Dominik Brodowski
2004-09-23 20:19 ` Pete Popov
2004-09-24 18:33   ` Pete Popov [this message]
2004-09-24 20:05     ` Dominik Brodowski
2004-09-24  8:15 ` Bruno Randolf

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=20040924183352.31414.qmail@web81407.mail.yahoo.com \
    --to=ppopov@embeddedalley.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=linux@dominikbrodowski.de \
    --cc=ralf@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