From: Dan Malek <dan@embeddededge.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Cort Dougan <cort@fsmlabs.com>, Matthew Locke <mlocke@mvista.com>,
akuster <akuster@dslextreme.com>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC/Patch] 4xx idle loop
Date: Thu, 25 Jul 2002 15:20:35 -0400 [thread overview]
Message-ID: <3D404F83.8010308@embeddededge.com> (raw)
In-Reply-To: 20020725162026.19919@192.168.4.1
Benjamin Herrenschmidt wrote:
> Well, while I tend to agree with you on this, experience proved that
> slightly abusing the ppc_md. indirection somewhat helped make the
> code cleaner (read: more self-contained, less cruft, ...)
All of the architectures except PowerPC seem to have a indirect
pointer to a power saving idle function from the idle loop. If
you don't want to follow this, we could have all of the board
specific files contain a 'power_save()' function, which could be
empty, always compile it and always call it. Today, the power
saving stuff is all 6xx/7xx/Mac specific, which kinda needs to
change if we want address the needs of embedded processors and
products.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-25 19:20 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
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 [this message]
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=3D404F83.8010308@embeddededge.com \
--to=dan@embeddededge.com \
--cc=akuster@dslextreme.com \
--cc=benh@kernel.crashing.org \
--cc=cort@fsmlabs.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 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.