From: Tejun Heo <tj@kernel.org>
To: Timur Tabi <timur@freescale.com>
Cc: linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: "ahci: drop intx manipulation on msi enable" breaks ULI M1575
Date: Tue, 07 Apr 2009 16:57:12 -0700 [thread overview]
Message-ID: <49DBE858.9040004@kernel.org> (raw)
In-Reply-To: <49DB6914.1030107@freescale.com>
Hello,
Timur Tabi wrote:
>> ahci: drop intx manipulation on msi enable
>>
>> There's no need to turn off intx explicitly on msi enable. This is
>> automatically handled by pci. Drop it.
>>
>> This might be needed on machines if the BIOS turns intx off during
>> boot. However, there's no evidence of such behavior for ahci and
>> the only such case seems to be ICH5 PATA according to ata_piix.
>> Also, given the way ahci operates, it's highly unlikely BIOS ever
>> disables IRQ for the controller. However, as this change has slight
>> possibility of introducing failure, please schedule it for #upstream.
>
> breaks SATA support on a Freescale MPC8610 HPCD (PowerPC) reference
> board. When I apply the patch, I get this result during boot:
...
> This board uses a ULI M1575 for SATA support.
>
> Unfortunately, I don't know enough about SATA or PCI interrupts to
> understand why you made the change or why it breaks on my board.
cc'ing Jeff.
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?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-04-07 23:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 14:54 "ahci: drop intx manipulation on msi enable" breaks ULI M1575 Timur Tabi
2009-04-07 23:57 ` Tejun Heo [this message]
2009-04-08 0:36 ` 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
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=49DBE858.9040004@kernel.org \
--to=tj@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).