From: Conn Clark <clark@esteem.com>
To: Patrick Mahoney <pmahoney@8d.com>
Cc: May Ling List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: mpc8xx - power save modes - PIT
Date: Thu, 10 Oct 2002 18:42:01 -0700 [thread overview]
Message-ID: <3DA62C69.A5BD884F@esteem.com> (raw)
In-Reply-To: 20021010230042.GA8690@segfault.usine.8d.com
Patrick Mahoney wrote:
>
> Conn,
>
> Thanks a lot for your reply.
>
> > I have played with some of the power saving modes on our custom
> > 850 board and have had no problems. I have toyed with the Doze High and
> > Doze Low modes in the idle loop. Attached is a hacked up idle loop for
> > kernel 2.4.19 that works for me.
>
>
> I recompiled and booted... it crashed on me! :( Maybe some differences
> with the platform... I'll look into that tomorrow.
>
I forgot to mention my kernel source tree was directly from kernel.org
When using my idle loop, does it crash right away or only when you try to
use the PIT?
>
>
> > Is there any particular reason you want to wake up the processor with
> > the PIT instead of just letting any old interrupt wake it up?
>
> Well i'd just like to be able to say : "im going to sleep. please wake
> me in 5 seconds". If theres an easier way, please enlighten me! :)
Well if you put the power saving code in the idle loop, when there
isn't anything to do the processor sleeps. When an interrupt happens it
wakes up to service the interrupt then checks to see if it is needed for
other things and if not it goes back to bed (much like me ;-)). If you need
to do something 5 seconds later a sleep call should do the trick unless
you need more precision.
>
> > You should be able to drop my idle.c in place of the old one. To disable
> > my hack just comment out the #define MPC8XX_POWERSAVE . My comments
> > shouldn't be to hard to understand. Also I have the SCCR[PRQEN] and the
> > SCCR[CRQEN] bits set.
>
> Yep, i'll dig into it tomorrow. I'm kind of allergic to inline
> assembly, but it's allright... ill have some pills! ;)
>
I had it all in C at one point which worked. I have to disable
interrupts and I don't like to be in this state any longer than I have to.
Its a practice I got driven into my head from my Z80 days. Besides, the
inline asm is quicker and smaller and saves you more power because you get
the processor to sleep sooner ;-) . If we all wrote our idle loops in
assembly we could get nothing done a lot quicker.
>
> Once again, thanks a lot for your help.
> Best regards,
>
> Pat Mahoney
If you find something out please let me know.
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/
next prev parent reply other threads:[~2002-10-11 1:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 18:35 mpc8xx - power save modes - PIT Patrick Mahoney
2002-10-10 21:49 ` Conn Clark
2002-10-10 23:00 ` Patrick Mahoney
2002-10-11 1:42 ` Conn Clark [this message]
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
-- 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-16 6:00 Cameron Rich
2002-10-16 13:22 ` Patrick Mahoney
2002-10-16 20:00 ` Conn Clark
2002-10-17 19:58 ` Patrick Mahoney
2002-10-17 21:50 ` Conn Clark
2002-10-16 17:29 ` 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=3DA62C69.A5BD884F@esteem.com \
--to=clark@esteem.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.