public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: "Li,
	Feng (GE Healthcare)"
	<Feng.Li-sCFLEkgZW7GbXiaaNHstOg@public.gmane.org>
Cc: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Could not deliver interrupts to the PCI board
Date: Mon, 07 Mar 2005 10:12:17 -0700	[thread overview]
Message-ID: <1110215537.21176.18.camel@eeyore> (raw)
In-Reply-To: <D02325A0F0177A468FD385A98178C53E0C3DF60A-5f9O7Fn4wvickVo8Y7U6IZteJpo0ey06@public.gmane.org>

On Mon, 2005-03-07 at 10:50 +0800, Li, Feng (GE Healthcare) wrote:
>      I am trying to port our old pci drivers from Linux 2.4 kernel to Linux 2.6 kernel.
> Now i am working in Linux 2.6.11. I found a strange problem , after i installed the new driver(based on 2.6.11 kernel)
> into kernel, our pci device is recognized as IO-APIC-edge,  and no interrupts can be catched by our driver.( The PCI device shuold be a 
> IO-APIC-level type)

Make sure that your driver calls pci_enable_device() before
looking at dev->irq.  We now use that hook to do interrupt
routing (enable link devices, set to level triggered mode,
etc).

>      So we disabled the ACPI service and restart the computer again, then the pci device can be recognized as
> IO-APIC-level, the driver works well! I think,there are maybe some changes in 2.6.11 for ACPI sleep 
> and hibernate that essentially puts ACPI in control of interrupts for many devices.Should i  need to add ACPI 
> declaration data to the driver ?

You should not need to add any ACPI smarts to your driver if
it does the pci_enable_device() correctly.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      parent reply	other threads:[~2005-03-07 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07  2:50 Could not deliver interrupts to the PCI board Li, Feng (GE Healthcare)
     [not found] ` <D02325A0F0177A468FD385A98178C53E0C3DF60A-5f9O7Fn4wvickVo8Y7U6IZteJpo0ey06@public.gmane.org>
2005-03-07 17:12   ` Bjorn Helgaas [this message]

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=1110215537.21176.18.camel@eeyore \
    --to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
    --cc=Feng.Li-sCFLEkgZW7GbXiaaNHstOg@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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