Michael Ellerman wrote:
On Tue, 2009-04-07 at 19:36 -0500, Timur Tabi wrote:
On Tue, Apr 7, 2009 at 6:57 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
Hmmm... that means intx isn't set by default. I'm not sure what is
the right thing to do here. I think it's something which should be
handled by the PCI layer. Oh well, maybe we should just revert the
change and keep setting intx?
cc'ing linuxppc-dev
I really don't know what should be done. It seems to make sense to
have the PCI layer enable interrupts.
This seems to be a powerpc-specific bug, but I don't know enough of
the PCI subsystem.
Have you confirmed that INTX is disabled before that call?
The symptoms definitely indicate such, as well as his reversing that commit.
My guess is that this is a ULI M1575-specific bug, and the PCI layer
needs a quirk that knows this device does -not- disable INTX, when MSI
is enabled.
But honestly, I never saw any harm in disabling INTX manually. Indeed,
I wrote the code that disabled INTX out of now-substantiated paranoia
that some PCI devices would be too dumb to follow that particular MSI
rule... and the cost of twiddling INTX seemed quite low in comparison
the potential problems created by the absence of INTX twiddling.
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
