public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca <kronos-0Y2hHv2PMqFeoWH0uzbU5w@public.gmane.org>
To: "Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
Subject: Re: pci device resume too early?
Date: Wed, 28 Jul 2004 23:06:02 +0200	[thread overview]
Message-ID: <20040728210602.GA26087@dreamland.darkstar.lan> (raw)
In-Reply-To: <200407282118.52624.stefandoesinger-RbZlAiThDcE@public.gmane.org>

Il Wed, Jul 28, 2004 at 09:18:52PM +0200, Stefan Dösinger ha scritto: 
> I moved device_resume(); in suspend_finish to be called after 
> pm_ops->finish(state); and my system resumes MUCH nicer.
> Sound resume works, usb-uhci resume works, ehci pci restore works. My suspend 
> script will shink a lot.
> 
> That's what suspend_finish looks like:
> 
> static void suspend_finish(u32 state)
> {
> 	if (pm_ops && pm_ops->finish)
> 		pm_ops->finish(state);
> 	device_resume();	/*Call it after pm_ops->finish*/	
> 	thaw_processes();
> 	pm_restore_console();
> }

Well, it may work but it's not correct. ->finish is meant to be called
to finalize the wakeup procedure *after* devices are waked up.

ACPI finish calls acpi_leave_sleep_state() and restore the waking
vectore. I'm not an ACPI guru but my guess is that what you need is
in acpi_leave_sleep_state().

If that's the case we may want to split the finish callback (say
prepare_wake and finish_wake).

Luca
-- 
Home: http://kronoz.cjb.net
"In linea di principio sarei indifferente al natale, se solo il natale
 ricambiasse la cortesia e mi lasciasse in pace." -- Marco d'Itri


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click

  parent reply	other threads:[~2004-07-28 21:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 17:53 pci device resume too early? Stefan Dösinger
     [not found] ` <200407281953.39159.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-07-28 18:14   ` Matthew Garrett
     [not found]     ` <1091038485.15464.9.camel-myFlNLNQP+Q@public.gmane.org>
2004-07-28 19:18       ` Stefan Dösinger
     [not found]         ` <200407282118.52624.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-07-28 21:06           ` Luca [this message]
     [not found]             ` <20040728210602.GA26087-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
2004-07-29 15:04               ` Stefan Dösinger
2004-08-04 18:47               ` Stefan Dösinger
2004-07-28 21:59           ` Matthew Garrett
  -- strict thread matches above, loose matches on Subject: below --
2004-07-29  0:48 Li, Shaohua

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=20040728210602.GA26087@dreamland.darkstar.lan \
    --to=kronos-0y2hhv2pmqfeowh0uzbu5w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
    --cc=stefandoesinger-RbZlAiThDcE@public.gmane.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