linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: akuster <akuster@dslextreme.com>
To: Matthew Locke <mlocke@mvista.com>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC/Patch] 4xx idle loop
Date: Wed, 24 Jul 2002 22:38:17 -0700	[thread overview]
Message-ID: <3D3F8EC9.7070105@dslextreme.com> (raw)
In-Reply-To: 3D3F04F7.1020005@mvista.com


Matthew Locke wrote:
>
>
> Rather than replace the whole idle loop, I would allow for
> sub-arch/processor specific code in the idle loop.  Perhaps move the
> power_save routine into the platform code?
>

This sounds like a good idea if we could use
  if( ppc_md.powersave != NULL)
       ppc_md.powersave();

If it is determined that calling power_save() which is resides in an
arch/processor specific file then we are talking about many files being
hit.  and the current power_save seems to common for many other ppc
platforms other than 4xx & 8xx

armin


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

  reply	other threads:[~2002-07-25  5:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24  5:55 [RFC/Patch] 4xx idle loop akuster
2002-07-24 19:50 ` Matthew Locke
2002-07-25  5:38   ` akuster [this message]
2002-07-25  5:39     ` cort
2002-07-25  6:54       ` cort
2002-07-25 16:51       ` Matthew Locke
2002-07-25 16:53         ` Cort Dougan
2002-07-25 16:20           ` Benjamin Herrenschmidt
2002-07-25 17:55             ` Cort Dougan
2002-07-25 18:04             ` Todd Poynor
2002-07-25 19:20             ` Dan Malek
2002-07-27 16:30               ` akuster

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=3D3F8EC9.7070105@dslextreme.com \
    --to=akuster@dslextreme.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mlocke@mvista.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).