From: Micheal Marineau <marineam@engr.orst.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][help?] Radeonfb acpi resume
Date: Tue, 12 Jul 2005 22:31:42 -0700 [thread overview]
Message-ID: <42D4A73E.4060509@engr.orst.edu> (raw)
In-Reply-To: <1121214768.31924.412.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 2989 bytes --]
Thanks for the input,
Benjamin Herrenschmidt wrote:
> On Sun, 2005-07-10 at 15:19 -0700, Micheal Marineau wrote:
>
>>I've been forward porting this patch for a while now and need
>>some input on it. You can see the last time someone posted it
>>to the list here:
>>http://www.ussg.iu.edu/hypermail/linux/kernel/0410.0/0600.html
>>
>>The big issue mentioned in that thread, that it reqires a key
>>press during the resume process to keep going still exists and
>>I have been unable to understand why. The issue is in radeon_pm.c
>>in this block that follows the last hunk of the diff:
>>
>> if (rinfo->no_schedule) {
>> if (try_acquire_console_sem())
>> return 0;
>> } else
>> acquire_console_sem();
>>
>>Specificly it's acquire_console_sem(); where the resume stops waiting
>>for a key press. What could be stopping things?
>
>
> I don't see any reason for that. That definitely shouldn't happen.
>
> .../...
Yea, so it would seem. Hopefully that'll get fixed magicly once I
clean up the rest a little bit.
>
>
>>diff -ru linux-2.6.12.orig/drivers/video/aty/radeon_pm.c
>>linux-2.6.12/drivers/video/aty/radeon_pm.c
>>--- linux-2.6.12.orig/drivers/video/aty/radeon_pm.c 2005-06-17
>>12:48:29.000000000 -0700
>>+++ linux-2.6.12/drivers/video/aty/radeon_pm.c 2005-07-03
>>19:55:36.000000000 -0700
>>@@ -2606,10 +2606,13 @@
>>
>> done:
>> pdev->dev.power.power_state = state;
>>+ pci_save_state (pdev);
>>
>> return 0;
>> }
>
>
> Hrm... radeonfb already saves the config space elsewhere. Note that it
> could maybe be converted to pci_save_state() / pci_restore_state() but
> currently, I do my own as I use that for "testing" if the card is still
> in it's previous state or was shut down. (I could probably use the
> content of a register instead, like CLK_PIN_CNTL)
Hrm, maybe it works now, but a few kernel versions back something broke
and I added that in as an easy fix. I'll try taking pci_save/restore out
again, hopefully all is well again.
>
>
>>+extern void acpi_vgapost (unsigned long slot);
>>+
>> int radeonfb_pci_resume(struct pci_dev *pdev)
>> {
>> struct fb_info *info = pci_get_drvdata(pdev);
>>@@ -2619,6 +2622,12 @@
>> if (pdev->dev.power.power_state == 0)
>> return 0;
>>
>>+ if (pdev->dev.power.power_state != 4)
>>+ {
>>+ pci_restore_state (pdev);
>>+ acpi_vgapost (pdev->devfn);
>>+ }
>>+
>> if (rinfo->no_schedule) {
>> if (try_acquire_console_sem())
>> return 0;
>
>
> The above will probably blow up anything that is not an x86 with ACPI.
> Besides there is already a mecanism in that file for calling functions
> for re-posting cards (since I have code to explicitely re-post rv280 and
> rv350 mobility on macs), you should hook into that existing mecanism
> when you detect ACPI.
>
> Ben.
>
ok, I haven't looked at the existing code very extensivly, I should check
it out :-)
--
Michael Marineau
marineam@engr.orst.edu
Oregon State University
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
prev parent reply other threads:[~2005-07-13 5:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-10 22:19 [PATCH][help?] Radeonfb acpi resume Micheal Marineau
2005-07-10 22:23 ` Micheal Marineau
2005-07-11 15:11 ` Pavel Machek
2005-07-11 18:50 ` Micheal Marineau
2005-07-11 18:56 ` Pavel Machek
2005-07-12 4:32 ` Micheal Marineau
[not found] ` <E1DsHSJ-0006kr-00@chiark.greenend.org.uk>
2005-07-12 13:39 ` Micheal Marineau
2005-07-13 0:32 ` Benjamin Herrenschmidt
2005-07-13 5:31 ` Micheal Marineau [this message]
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=42D4A73E.4060509@engr.orst.edu \
--to=marineam@engr.orst.edu \
--cc=benh@kernel.crashing.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