linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] ppc32: pmac sleep support update
Date: Fri, 04 Feb 2005 09:15:01 +1100	[thread overview]
Message-ID: <1107468901.2363.40.camel@gaston> (raw)
In-Reply-To: <20050203125725.GA20087@suse.de>

On Thu, 2005-02-03 at 13:57 +0100, Olaf Hering wrote:
>  On Tue, Jan 18, Benjamin Herrenschmidt wrote:
> 
> > Hi !
> > 
> > This patch updates the PowerMac sleep support. The ability to sleep is now broken
> > into 2 different flags, one, "may sleep" is set for all motherboards that we know
> > how to put to sleep and wakeup. It gets turned into "can sleep" upon a call from
> > the video driver indicating the ability to wakeup the video card. This doesn't
> > deal with head-less machines, but this can be improved later. It also adds better
> > cache flush code, which improves stability with cpufreq as well as sleep.
> > 
> > This patch actually breaks sleep support until the video drivers for the affected
> > machines have been updated. This will come as separate patches.
> 
> Is that supposed to work? 2.6.11-rc2-bk10 sleeps ok on a pismo, but -rc3
> just does nothing when closing the lid.

It's normal, the kernel is waiting for the video driver to do a platform
call to indicate it supports sleep/wakeup on this model. The video
driver updates haven't been pushed yet. This concerns laptops with
nVidia, r128 and radeon chips. The former, we don't know how to wake
them up yet, the r128 patch is trivial and should go in, the radeonfb
patch is still beeing debated on.

Ben.

  reply	other threads:[~2005-02-03 22:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18  1:32 [PATCH] ppc32: pmac sleep support update Benjamin Herrenschmidt
2005-01-19  1:37 ` Andreas Schwab
2005-01-19  2:04   ` Benjamin Herrenschmidt
2005-01-19 21:49     ` Andreas Schwab
2005-01-19 22:57       ` Benjamin Herrenschmidt
2005-01-20  0:43         ` Andreas Schwab
2005-01-20  1:01           ` Benjamin Herrenschmidt
2005-01-20  1:34             ` Andreas Schwab
2005-01-20  2:23               ` Benjamin Herrenschmidt
2005-01-19 13:45 ` David Woodhouse
2005-01-19 22:44   ` Benjamin Herrenschmidt
2005-02-03 12:57 ` Olaf Hering
2005-02-03 22:15   ` Benjamin Herrenschmidt [this message]
2005-02-26 11:28 ` Olaf Hering
2005-02-27  0:24   ` Benjamin Herrenschmidt

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=1107468901.2363.40.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olh@suse.de \
    --cc=torvalds@osdl.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).