public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
To: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
Cc: stefandoesinger-RbZlAiThDcE@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Pallipadi,
	Venkatesh"
	<venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Linux Kernel list
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Li,
	Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
Date: Fri, 20 Aug 2004 16:43:31 -0400	[thread overview]
Message-ID: <41266273.1010604@optonline.net> (raw)
In-Reply-To: <4126621B.3090701-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]


Oops. Forgot the patch again. See attached.

Nathan Bryant wrote:

> Stefan Dösinger wrote:
>
>> If I re-programm the IRQ to something else than IRQ10, the device 
>> doesn't resume too. So it's not only a problem of IRQ 11.
>>  
>>
> Seems like an anything-at-all-other-than-IRQ-10 problem. If the 
> current thinking is right, your BIOS is assigning IRQ10 during boot, 
> so moving it anywhere else is what causes problems.
>
> But the current thinking doesn't quite seem right, because it seeems 
> like we're seeing these problems after the irqrouter is resumed. Can 
> you verify that with the attached patch? The patch should give us 
> enough information as long as you've got the proper kernel loglevel set.
>
> Now, I wonder if the only reason it works when you set IRQ 10 is that 
> some other driver is unconditionally claiming the interrupt...
>
> Nathan
>
>> The ipw2100 driver calls pci_disable_device in it's suspend handler. 
>> But I think the ipw2100 maintainers need help with suspend/resume 
>> because James Ketrenos can't test it on his own system.
>>  
>>
> pci_disable_device() only turns off bus-mastering, it doesn't unmap 
> the I/O or disable the slot. Maybe we also need to set power state D3 
> and do a device-specific disable-interrupts, but I think D0 gets 
> restored for us pretty early during resume anyway...
>
> Anyway, something doesn't quite add up...
>
> Nathan
>



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: pci_linkdebug.patch --]
[-- Type: text/x-patch; name=pci_linkdebug.patch, Size: 410 bytes --]

===== drivers/acpi/pci_link.c 1.32 vs edited =====
--- 1.32/drivers/acpi/pci_link.c	2004-08-18 19:26:48 -04:00
+++ edited/drivers/acpi/pci_link.c	2004-08-20 16:28:40 -04:00
@@ -717,6 +717,8 @@
 
 	ACPI_FUNCTION_TRACE("irqrouter_resume");
 
+	printk(KERN_DEBUG "irqrouter_resume: called.\n");
+
 	list_for_each(node, &acpi_link.entries) {
 
 		link = list_entry(node, struct acpi_pci_link, node);


  parent reply	other threads:[~2004-08-20 20:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 19:00 [PATCH][RFC] fix ACPI IRQ routing after S3 suspend Pallipadi, Venkatesh
2004-08-20 19:42 ` [ACPI] " Nathan Bryant
     [not found]   ` <41265443.9050800-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-20 20:01     ` Stefan Dösinger
     [not found]       ` <200408202201.54083.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-20 20:42         ` Nathan Bryant
     [not found]           ` <4126621B.3090701-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-20 20:43             ` Nathan Bryant [this message]
2004-08-20 20:17     ` Stefan Dösinger
     [not found] <412B2E16.1040904@optonline.net>
     [not found] ` <20040824123913.GD25947@gamma.logic.tuwien.ac.at>
     [not found]   ` <20040824123913.GD25947-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>
2004-08-24 13:23     ` Nathan Bryant
     [not found] ` <20040824142219.GA13607@gamma.logic.tuwien.ac.at>
     [not found]   ` <20040824142219.GA13607-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>
2004-08-24 14:32     ` Nathan Bryant
     [not found]       ` <412B516B.8030704-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-25 11:19         ` Norbert Preining
  -- strict thread matches above, loose matches on Subject: below --
2004-08-04  2:36 Li, Shaohua
     [not found] ` <B44D37711ED29844BEA67908EAF36F037BB9C6-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-04  2:55   ` Len Brown
2004-08-04  1:42 Nathan Bryant
     [not found] ` <41103F22.4090303-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-04  2:59   ` Len Brown
2004-08-04 15:57     ` Nathan Bryant
2004-08-19 20:24 ` [ACPI] " Stefan Dösinger
     [not found]   ` <200408192224.08271.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-19 20:54     ` Nathan Bryant

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=41266273.1010604@optonline.net \
    --to=nbryant-p32f3xycuykqczcgjluoxw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=stefandoesinger-RbZlAiThDcE@public.gmane.org \
    --cc=venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@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