[PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks.

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-kernel@...>
Cc: <jeff@...>, <barkalow@...>, <linas@...>, <chunhao.huang@...>, <gregkh@...>, <htejun@...>, <brice.goglin@...>, <david.gaarenstroom@...>, <linux-pci@...>, <shane.huang@...>, <linux-ide@...>, <brice@...>, <mchan@...>
Date: Tuesday, October 23, 2007 - 10:51 pm

The forthcoming patches are also available from:

	kernel.org:/pub/scm/linux/kernel/git/davem/msiquirk-2.6.git

and clean up the handling of the common quirk wherein setting
INTX_DISABLE will mistakedly disable MSI generation for some
devices.

For devices without that problem, we want to keep the pci_intx() calls
in drivers/pci/msi.c because those help protect against devices
with the opposite problem.  Such devices always generate INTX
interrupts even when MSI is enabled, unless INTX_DISABLE is set.

Michael, please pay special attention to patch #3.  I think I
picked the correct PCI device IDs to match for the quirk
(5714* and 5780*) but it's possible we might need more elaborate
checks here.  It at least worked properly for the chips in my
Niagara system.

In addition to the Tigon3 cases, I added quirk entries for the
SB700/800 SATA chips and the IXP SB400 USB controllers.

Signed-off-by: David S. Miller <davem@davemloft.net>
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks., David Miller, (Tue Oct 23, 10:51 pm)
Re: [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks., Jeff Garzik, (Thu Oct 25, 1:37 am)
Re: [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks., Daniel Barkalow, (Wed Oct 24, 12:58 am)
Re: [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks., David Miller, (Wed Oct 24, 1:06 am)
Re: [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks., Daniel Barkalow, (Wed Oct 24, 12:52 pm)