From: "Mark A. Greer" <mgreer@mvista.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Matt Porter <porter@cox.net>,
Tom Rini <trini@kernel.crashing.org>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC/PATCH] idle loop changes
Date: Wed, 31 Jul 2002 17:48:31 -0400 [thread overview]
Message-ID: <3D485B2F.84829A96@mvista.com> (raw)
In-Reply-To: 3D48569D.30201@embeddededge.com
Dan Malek wrote:
> Matt Porter wrote:
>
> > So, some new machdep calls that you can populate on a per board basis?
> > Are you just talking about them being used upon entering/exiting idle?
>
> I was just thinking the power_save() function could be unique to a
> board. It has to be something combined with the power save mode
> chosen on the chip, so machdep calls may not be appropriate. We are
> using names like ppc6xx_pm_idle, ppc4xx, ppc8xx, when it could be
> my_custom_board_pm_idle......Just don't assume one type of chip will
> use the same function on different boards. When the idle/power save
> function is chosen, it should probably be done during board setup,
> not processor set up.
Why not use keep the ppc6xx_pm_idle, etc. as fallbacks (e.g., nothing
special about your board so use generic 6xx one) and still use machdep
calls so its easy to override in case there is something special you need
to do for your board?
Mark
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-07-31 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 19:32 [RFC/PATCH] idle loop changes Tom Rini
2002-07-31 20:25 ` Dan Malek
2002-07-31 20:38 ` Tom Rini
2002-07-31 20:41 ` Tom Rini
2002-07-31 21:33 ` Matt Porter
2002-07-31 21:29 ` Dan Malek
2002-07-31 21:48 ` Mark A. Greer [this message]
2002-07-31 22:23 ` Dan Malek
2002-08-01 0:11 ` Tom Rini
2002-07-31 21:24 ` Matt Porter
2002-08-01 0:09 ` Tom Rini
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=3D485B2F.84829A96@mvista.com \
--to=mgreer@mvista.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=porter@cox.net \
--cc=trini@kernel.crashing.org \
/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).