linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: "Mark A. Greer" <mgreer@mvista.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 18:23:12 -0400	[thread overview]
Message-ID: <3D486350.8070700@embeddededge.com> (raw)
In-Reply-To: 3D485B2F.84829A96@mvista.com


Mark A. Greer wrote:

> Why not use keep the ppc6xx_pm_idle, etc. as fallbacks (e.g., nothing
> special about  your board so use generic 6xx one)

That's fine, except we aren't using machdep calls.  The interaction between
the external devices and the processor control may not allow (or we may
not desire) using a "standard" processor function.  For example, the MPC8xx
has four powersave modes and four sleep modes.  Only one of the modes
is generic and isn't suitable to use if I use one of the other modes that
may require external device management.

My comment was truly simple :-)  Just don't assume the processor powersave
modes are suitable for all boards.  A board may wish to do something
different, so I suggest keeping the power save function initialization local
to a board rather than processor architecture.  Many of them are likely to
be generic and can use the same function, just allow the provision for them
to be different at the board level, that's all.

Thanks.


	-- Dan


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

  reply	other threads:[~2002-07-31 22:23 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
2002-07-31 22:23         ` Dan Malek [this message]
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=3D486350.8070700@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mgreer@mvista.com \
    --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).