[RFC] ACPI vs device ordering on resume

2006-11-14 Thread Stephen Hemminger
If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 driver, the first interrupt gets misrouted to the original shared IRQ, rather than to the MSI irq expected. During the pci_restore process, the MSI information and the PCI command register are restored properly. But later durin

Re: [RFC] ACPI vs device ordering on resume

2006-11-14 Thread Linus Torvalds
On Tue, 14 Nov 2006, Stephen Hemminger wrote: > > During the pci_restore process, the MSI information and the PCI command > register > are restored properly. But later during resume, inside the ACPI evaluation of > the WAK method, the PCI_COMMAND INTX_DISABLE (0x400) flag is being cleared. >

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-11-14 Thread Len Brown
On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote: > If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 driver, > the first interrupt gets misrouted to the original shared IRQ, rather than > to the MSI irq expected. > > During the pci_restore process, the MSI information

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-11-15 Thread Rafael J. Wysocki
On Wednesday, 15 November 2006 08:03, Len Brown wrote: > On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote: > > If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 driver, > > the first interrupt gets misrouted to the original shared IRQ, rather than > > to the MSI irq exp

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-11-15 Thread Linus Torvalds
On Wed, 15 Nov 2006, Len Brown wrote: > > So it looks like we need this sequence: > > enable_nonboot_cpus() /* INIT */ > finish() /* _WAK */ > device_resume() Can somebody remind me about this immediately after 2.6.19? No way am I going to make that kind of a major ordering change right

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-11-30 Thread Stephen Hemminger
On Wed, 15 Nov 2006 02:03:30 -0500 Len Brown <[EMAIL PROTECTED]> wrote: > On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote: > > If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 driver, > > the first interrupt gets misrouted to the original shared IRQ, rather than > >

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Pavel Machek
Hi! > > So it looks like we need this sequence: > > > > enable_nonboot_cpus() /* INIT */ > > finish()/* _WAK */ > > device_resume() > > Can somebody remind me about this immediately after 2.6.19? Remind. But note that freezer is not yet SMP safe... Rafael is working on that.

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Rafael J. Wysocki
On Friday, 1 December 2006 02:48, Stephen Hemminger wrote: > On Wed, 15 Nov 2006 02:03:30 -0500 > Len Brown <[EMAIL PROTECTED]> wrote: > > > On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote: > > > If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 > > > driver, > > > t

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Rafael J. Wysocki
Hi, On Friday, 1 December 2006 10:33, Pavel Machek wrote: > Hi! > > > > So it looks like we need this sequence: > > > > > > enable_nonboot_cpus() /* INIT */ > > > finish() /* _WAK */ > > > device_resume() > > > > Can somebody remind me about this immediately after 2.6.19? > > Remind. But note

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Pavel Machek
Hi! > > > > So it looks like we need this sequence: > > > > > > > > enable_nonboot_cpus() /* INIT */ > > > > finish()/* _WAK */ > > > > device_resume() > > > > > > Can somebody remind me about this immediately after 2.6.19? > > > > Remind. But note that freezer is not yet SMP safe... Ra

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Rafael J. Wysocki
Hi, On Friday, 1 December 2006 11:57, Pavel Machek wrote: > Hi! > > > > > > So it looks like we need this sequence: > > > > > > > > > > enable_nonboot_cpus() /* INIT */ > > > > > finish() /* _WAK */ > > > > > device_resume() > > > > > > > > Can somebody remind me about this immediately aft

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Linus Torvalds
On Fri, 1 Dec 2006, Pavel Machek wrote: > > > So it looks like we need this sequence: > > > > > > enable_nonboot_cpus() /* INIT */ > > > finish() /* _WAK */ > > > device_resume() > > > > Can somebody remind me about this immediately after 2.6.19? > > Remind. But note that freezer is not yet

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Alexey Starikovskiy
Linus Torvalds wrote: On Fri, 1 Dec 2006, Pavel Machek wrote: So it looks like we need this sequence: enable_nonboot_cpus() /* INIT */ finish()/* _WAK */ device_resume() Can somebody remind me about this immediately after 2.6.19? Remind. But note that freezer is no

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Stephen Hemminger
On Fri, 01 Dec 2006 20:45:51 +0300 Alexey Starikovskiy <[EMAIL PROTECTED]> wrote: > Linus Torvalds wrote: > > On Fri, 1 Dec 2006, Pavel Machek wrote: > > > > > So it looks like we need this sequence: > > enable_nonboot_cpus() /* INIT */ > finish() /* _WAK */ > device_re

Re: [linux-pm] [RFC] ACPI vs device ordering on resume

2006-12-01 Thread Alexey Starikovskiy
Stephen Hemminger wrote: On Fri, 01 Dec 2006 20:45:51 +0300 Alexey Starikovskiy <[EMAIL PROTECTED]> wrote: Linus Torvalds wrote: On Fri, 1 Dec 2006, Pavel Machek wrote: So it looks like we need this sequence: enable_nonboot_cpus() /* INIT */ finish()/* _WAK */ devi