RE: "irq 11: nobody cared" after S3

Li, Shaohua
2004-08-03T01:43:22Z

Actually current ACPI drivers don't support resume/suspend. :(. I also
consider adding a workaround to support Link device suspend/resume, but
you know it's just a workaround. Some guys may not agree to add a
workaround for the special case. For long term, LPC bridge driver should
do this.

Thanks,
Shaohua

>-----Original Message-----
>From: Nathan Bryant [mailto:nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org]
>Sent: Tuesday, August 03, 2004 9:28 AM
>To: Li, Shaohua
>Cc: stefandoesinger-RbZlAiThDcE@public.gmane.org; acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>Subject: Re: [ACPI] "irq 11: nobody cared" after S3
>
>Li, Shaohua wrote:
>
>>I don't think your patch works, and even it works for your system, it
>>will break other systems. The goal of 'setonboot' is to prevent
setting
>>LINK device's IRQ every time, which we added last year. Without it,
many
>>systems will break. IIRC, its goal is to resolve a bug in bugzilla.
But
>>currently I don't remember the exact bug number.
>>
>>
>Thanks for the feedback. It works for my system--but only for devices
>that call pci_device_enable(). Therefore I am currently reinstating the
>"setonboot" flag and reworking the patch along the lines of the