From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] fbdev and power management
Date: 09 Jul 2003 13:35:58 +0200 [thread overview]
Message-ID: <1057750557.514.22.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0307090024170.32323-100000@phoenix.infradead.org>
> No patches at this time. I need to learn the new power management code.
> Where are the docs for them ?
The PM code in radeonfb is probably only useful for Mac laptops where
we have to manually put the chip in D2 state. I don't think x86 laptops
use D2...
Note that I have a patch adding some basic PM support to fbdev in 2.5
that I need to send you for review. The PM is always initiated by the
low level driver which gets notified of PM events by its parent bus,
what I added is a way for the driver to "broadcast" that to clients
like fbcon so fbcon can stop touching the framebuffer while the chip
is potentially off, and can restore the display on wakeup.
I'll send that to you asap.
Note: The Power Management isn't well implemented in 2.5 yet. The
infrastructure is mostly there, but the driver side semantics are
still wrong. Patrick Mochel has a new implementation that is much
better, but he didn't merge it upstream yet. I expect this will
happen around Kernel Summit / OLS.
Ben.
next prev parent reply other threads:[~2003-07-09 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030704042052.GL4359@himi.org>
2003-07-08 23:25 ` fbdev and power management James Simmons
2003-07-09 11:35 ` Benjamin Herrenschmidt [this message]
2003-07-09 14:10 ` [Linux-fbdev-devel] " Russell King
2002-01-05 11:13 ` Pavel Machek
2003-07-14 16:34 ` Benjamin Herrenschmidt
2003-07-14 20:11 ` Pavel Machek
2003-07-09 17:45 ` James Simmons
2003-07-09 17:49 ` 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=1057750557.514.22.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).