From: Cort Dougan <cort@fsmlabs.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: 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 11:55:40 -0600 [thread overview]
Message-ID: <20020725115540.L2276@host110.fsmlabs.com> (raw)
In-Reply-To: <20020725162026.19919@192.168.4.1>; from benh@kernel.crashing.org on Thu, Jul 25, 2002 at 06:20:26PM +0200
That can be implemented within the arch_idle() for the given chip type. If
6xx chips want to do some pmac specific idle it can have a table of its
own or look int ppc_md.board_specific_power_save. On 4xx there may not
be a need for that so there's no need for the indirection.
The chip idle is invariant after the compile but the board specific idle
may or may not be so push that into the chip specific function. That way
no indirection is forced on configurations that don't need it.
} 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, ...)
}
} Also, in this specific case, we might well want to have an machine
} specific power saving feature: I've had various tweaks in mind for
} powermac laptops that I never ended up implementing...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-25 17:55 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 [this message]
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=20020725115540.L2276@host110.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=akuster@dslextreme.com \
--cc=benh@kernel.crashing.org \
--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).