public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Dösinger" <stefandoesinger@gmx.at>
To: acpi-devel@lists.sourceforge.net
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	"Brown, Len" <len.brown@intel.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	Nathan Bryant <nbryant@optonline.net>
Subject: Re: [ACPI] [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
Date: Fri, 20 Aug 2004 22:01:54 +0200	[thread overview]
Message-ID: <200408202201.54083.stefandoesinger@gmx.at> (raw)
In-Reply-To: <41265443.9050800@optonline.net>


> Something else to watch out for on ICH2 and similar chipsets is that, as
> long as the IRQ router is steering a PCI link onto a certain IRQ, LPC
> ISA device are blocked from triggering that IRQ via the SERIRQ protocol.
> But if we move the all the PCI links elsewhere, the SERIRQ is no longer
> blocked, and if some ISA LPC device is holding a high level, which
> normally wouldn't trigger IRQ's under ISA, then the IRQ line will get
> disabled because the PIC is probably set to level-trigger because it was
> PCI at one point. I've seen this happen with IRQ 12 when the BIOS
> decided there was no PS/2 mouse present so it could re-use the IRQ. The
> real cause is that the i850 has  a register that allows IRQ1 and IRQ12
> to be disabled on the LPC bus, and this register isn't restored on
> resume. This probably doesn't apply to IRQ11 on Stefan's system, though...
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.

> Maybe it's time to look at the suspend/resume callbacks on the ipw2100
> driver, anyway.
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.

I'll change another devices IRQ line to test if it's only an ipw2100 issue.

Stefan

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 19:00 [ACPI] [PATCH][RFC] fix ACPI IRQ routing after S3 suspend Pallipadi, Venkatesh
2004-08-20 19:42 ` Nathan Bryant
2004-08-20 20:01   ` Stefan Dösinger [this message]
2004-08-20 20:42     ` Nathan Bryant
2004-08-20 20:43       ` Nathan Bryant
2004-08-20 20:17   ` Stefan Dösinger
  -- strict thread matches above, loose matches on Subject: below --
2004-08-23  5:58 Li, Shaohua
2004-08-04  1:42 Nathan Bryant
2004-08-19 20:24 ` [ACPI] " Stefan Dösinger
2004-08-19 20:54   ` Nathan Bryant
2004-08-20 10:50     ` Stefan Dösinger
2004-08-20 12:18       ` Nathan Bryant
2004-08-20 16:36         ` Stefan Dösinger

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=200408202201.54083.stefandoesinger@gmx.at \
    --to=stefandoesinger@gmx.at \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbryant@optonline.net \
    --cc=shaohua.li@intel.com \
    --cc=venkatesh.pallipadi@intel.com \
    /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