linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: michael@ellerman.id.au
Cc: Tejun Heo <tj@kernel.org>,
	linux-ide@vger.kernel.org, Timur Tabi <timur@freescale.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Linux PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: "ahci: drop intx manipulation on msi enable" breaks ULI M1575
Date: Wed, 08 Apr 2009 02:12:46 -0400	[thread overview]
Message-ID: <49DC405E.5050005@garzik.org> (raw)
In-Reply-To: <1239156559.10104.7.camel@localhost>

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@kernel.org> 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

  reply	other threads:[~2009-04-08  7:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49DB6914.1030107@freescale.com>
     [not found] ` <49DBE858.9040004@kernel.org>
2009-04-08  0:36   ` "ahci: drop intx manipulation on msi enable" breaks ULI M1575 Timur Tabi
2009-04-08  0:52     ` Michael Ellerman
2009-04-08  1:19       ` Timur Tabi
2009-04-08  2:09     ` Michael Ellerman
2009-04-08  6:12       ` Jeff Garzik [this message]
2009-04-08 11:40       ` Timur Tabi
2009-04-08 21:04         ` Tejun Heo
2009-04-08 21:06           ` Timur Tabi
2009-04-08 21:13             ` Tejun Heo
2009-04-08 21:17               ` Timur Tabi
2009-04-08 21:31                 ` Tejun Heo
2009-04-08 22:15                   ` Timur Tabi
2009-04-08 23:53                     ` Michael Ellerman
2009-04-09  4:23                       ` Kumar Gala
2009-04-09  4:38                         ` Michael Ellerman
2009-04-09  5:18                           ` Kumar Gala
2009-04-09  5:32                           ` Jeff Garzik
2009-04-09 15:19                             ` Timur Tabi
2009-04-13 11:34                             ` Michael Ellerman
2009-04-16 21:27                             ` Timur Tabi

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=49DC405E.5050005@garzik.org \
    --to=jeff@garzik.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=timur@freescale.com \
    --cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).