From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Moritz Muehlenhoff <jmm@inutil.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.12-rc2
Date: Fri, 08 Apr 2005 08:43:10 +1000 [thread overview]
Message-ID: <1112913790.9567.302.camel@gaston> (raw)
In-Reply-To: <20050407175026.GA5872@informatik.uni-bremen.de>
On Thu, 2005-04-07 at 19:50 +0200, Moritz Muehlenhoff wrote:
> Benjamin Herrenschmidt wrote:
> > > 1. When resuming from S3 suspend and having switched off the backlight
> > > with radeontool the backlight isn't switched back on any more.
> >
> > I'm not sure what's up here, it's a nasty issue with backlight. Can
> > radeontool bring it back ?
>
> Before suspending I power down the backlight with "radeontool light off"
> and with 2.6.11 the display is properly restored. With 2.6.12rc2 the
> backlight remains switched off and if I switch it on with radeontool it
> becomes lighter, but there's still no text from the fbcon, just the blank
> screen.
>
> > > 2. I'm using fbcon as my primary work environment, but tty switching has
> > > become _very_ sloppy, it's at least a second now, while with 2.6.11 it
> > > was as fast as a few ms. Is this caused by the "proper PLL accesses"?
> >
> > Yes. Unfortunately. It's surprised it is that slow though, there
> > shouldn't be more than 5 or 6 PLL accesses on a normal mode switch, with
> > 5ms pause for each, that should still be very reasonable. It looks like
> > we are doing a lot more accesses which I don't completely understand.
>
> Can you tell me which function you have in mind, so that I can insert
> some printks to see how often it's called?
radeon_pll_errata_after_data() calls radeon_msleep() (it's in
radeonfb.h)
Ben.
next prev parent reply other threads:[~2005-04-07 22:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0504040945100.32180@ppc970.osdl.org>
2005-04-04 21:32 ` Linux 2.6.12-rc2 Linus Torvalds
2005-04-04 22:58 ` Andres Salomon
2005-04-04 23:04 ` Andres Salomon
2005-04-04 23:07 ` Andres Salomon
2005-04-04 23:24 ` Al Viro
2005-04-04 23:49 ` Russell King
2005-04-04 23:54 ` Al Viro
2005-04-04 23:37 ` Stephen Rothwell
2005-04-04 23:54 ` Al Viro
2005-04-05 4:54 ` Gene Heskett
2005-04-06 17:14 ` Moritz Muehlenhoff
2005-04-06 22:42 ` Benjamin Herrenschmidt
2005-04-07 17:50 ` Moritz Muehlenhoff
2005-04-07 18:54 ` Nish Aravamudan
2005-04-07 22:45 ` Benjamin Herrenschmidt
2005-04-08 0:44 ` Nish Aravamudan
2005-04-08 6:28 ` AsterixTheGaul
2005-04-08 6:39 ` AsterixTheGaul
2005-04-08 7:00 ` AsterixTheGaul
2005-04-08 15:39 ` Nish Aravamudan
2005-04-08 18:14 ` AsterixTheGaul
2005-04-07 22:43 ` Benjamin Herrenschmidt [this message]
2005-04-05 7:29 Oleg Nesterov
2005-04-05 8:03 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 14:56 Hubert Tonneau
2005-04-06 23:20 Bob Gill
2005-04-06 23:25 ` Dave Jones
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=1112913790.9567.302.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jmm@inutil.org \
--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