linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: akuster <akuster@dslextreme.com>
To: akuster@dslextreme.com
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [RFC/Patch] ppc4xx_pm.c
Date: Thu, 25 Jul 2002 16:55:16 -0700	[thread overview]
Message-ID: <3D408FE4.2090602@dslextreme.com> (raw)
In-Reply-To: 3D3DD903.3070300@dslextreme.com

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

akuster wrote:
>
> I am in the process of fixing the init of the pm for 4xx in ppc4xx_pm.c
> so that it can be used and I and others have discussed having the
> drivers enable/disable their own power managment bits at init & exit times.
>
> So what I would like to do is have each core header define a default set
> of what is required to be powered on and then have each driver enable
> them selves.  These changes would be done in two stages
>
> 1) fix ppc4xx_pm.c init and have the default pm bitmap set to all ocp
> drivers on.

These patches are the changes to the core header files and for ppc4xx_pm.c.

  Please _note_ that if you enable the Power Managment in the config
that most kernels might hang if you use an ocp device since the drivers
are not updated yet. :)

If no one has an objection, then I will get it submitted

armin




[-- Attachment #2: pm_header_0724.patch.gz --]
[-- Type: application/x-gunzip, Size: 3229 bytes --]

[-- Attachment #3: ocp_pm_0724.patch.gz --]
[-- Type: application/x-gunzip, Size: 1093 bytes --]

  reply	other threads:[~2002-07-25 23:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 22:30 [RFC/Patch] ppc4xx_pm.c akuster
2002-07-25 23:55 ` akuster [this message]
2002-07-26 23:35 ` akuster
2002-07-27  0:04   ` Todd Poynor
2002-07-27 17:00     ` 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=3D408FE4.2090602@dslextreme.com \
    --to=akuster@dslextreme.com \
    --cc=linuxppc-dev@lists.linuxppc.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).