linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Conn Clark <clark@esteem.com>
To: Patrick Mahoney <pmahoney@8d.com>
Cc: Cameron Rich <CameronR@nulec.com.au>,
	May Ling List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc8xx - power save modes - PIT
Date: Wed, 16 Oct 2002 13:00:49 -0700	[thread overview]
Message-ID: <3DADC571.AF3050F4@esteem.com> (raw)
In-Reply-To: 20021016132208.GA16734@segfault.usine.8d.com


Patrick Mahoney wrote:
>
> > I've tried Conn's code, but I'm experiencing problems with PLPRCR[CSCR] as
> > being 1 all the time after a rfi. I am also occasionally seeing MSR_POW set
> > to 1 after the rfi return.
>
> Well the 2.4 Linux kernel does not support runtime modifications to
> the clock rate. So what's the point of playing with CSCR?

If the CPU is dozing The kernel will never know we changed it as long as
we change it back when the CPU wakes up.

>
> >
> > I can work around this problem by setting PLPRCR[CSCR] = 0 and MSR_POW = 0
> > after the rfi and this eventually works. But is this the solution? I'm also
> > noticing no great decrease in power consumption even though I've only got a
> > couple of (sleeping) processes. And it seems that there is (mostly) no time
> > between entering Doze Low mode and the rfi which confirms the unsatisfactory
> > power consumption figures.
>
> I notice no decrease at all!  :(

You may be expecting to much.

>
> I set both crqen and prqen in the bootloader. The idled routine gets
> entered and executed repeatedly, but no decrease in current
> consumption can be observed.
>
> Pat Mahoney

	Compile up a version of top and see how much time the CPU is Idle.

Good luck

	Conn
--

*****************************************************************
  If you live at home long enough, your parents will move out.
 (Warning they may try to sell their house out from under you.)
*****************************************************************

Conn Clark
Engineering Stooge				clark@esteem.com
Electronic Systems Technology Inc.		www.esteem.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-10-16 20:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16  6:00 mpc8xx - power save modes - PIT Cameron Rich
2002-10-16 13:22 ` Patrick Mahoney
2002-10-16 20:00   ` Conn Clark [this message]
2002-10-17 19:58     ` Patrick Mahoney
2002-10-17 21:50       ` Conn Clark
2002-10-16 17:29 ` Conn Clark
  -- strict thread matches above, loose matches on Subject: below --
2002-10-11 13:15 Steven Blakeslee
2002-10-11 16:08 ` Patrick Mahoney
2002-10-10 18:35 Patrick Mahoney
2002-10-10 21:49 ` Conn Clark
2002-10-10 23:00   ` Patrick Mahoney
2002-10-11  1:42     ` Conn Clark
2002-10-11 15:59       ` Patrick Mahoney
2002-10-11 17:05         ` Conn Clark
2002-10-11 17:17           ` Patrick Mahoney
     [not found]       ` <20021021133451.GA16540@segfault.usine.8d.com>
2002-10-21 15:52         ` Conn Clark
     [not found]   ` <20021015225625.GA8153@segfault.usine.8d.com>
2002-10-16  1:08     ` Conn Clark
2002-10-16 15:42       ` Patrick Mahoney
     [not found]       ` <20021016130153.GA16430@segfault.usine.8d.com>
2002-10-16 18:14         ` Conn Clark

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=3DADC571.AF3050F4@esteem.com \
    --to=clark@esteem.com \
    --cc=CameronR@nulec.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=pmahoney@8d.com \
    /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;
as well as URLs for NNTP newsgroup(s).