From: Timur Tabi <timur@freescale.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Tejun Heo <tj@kernel.org>,
Linux PPC Development <linuxppc-dev@ozlabs.org>,
linux-ide@vger.kernel.org
Subject: Re: "ahci: drop intx manipulation on msi enable" breaks ULI M1575
Date: Thu, 16 Apr 2009 16:27:59 -0500 [thread overview]
Message-ID: <ed82fe3e0904161427y4d4e7f4ewcf39956ab82d4de9@mail.gmail.com> (raw)
In-Reply-To: <49DD8871.2030404@garzik.org>
On Thu, Apr 9, 2009 at 12:32 AM, Jeff Garzik <jeff@garzik.org> wrote:
> 3) As a result, Timur's 'ahci' is no longer receiving interrupts. Presuma=
bly
> this means that BOTH of the following conditions are true
>
> =A0 =A0 =A0 =A0a) INTX is disabled
> =A0 =A0 =A0 =A0b) MSI is not available
>
> Today I am thinking we should either revert the libata commit
> (a5bfc4714b3f01365aef89a92673f2ceb1ccf246), or poke PCI to twiddle INTX f=
or
> us at pci_enable_device() time, perhaps.
We (Freescale) have discussed and debugged this issue, and I'm 99%
certain that we have a board-specific fix, so there's no need to
revert the patch.
According to the original developer, he had to disable the INTX on the
board if SATA were disabled, otherwise some other problem occurred.
He noticed that the interrupt was re-enabled (presumably by the
pre-patch code in ahci.c), so he thought it would be okay to disable
it.
I've run some tests, and so far it appears that the problem does not
occur with the latest kernel (or the latest revision of the hardware).
I need to run some more tests to be absolutely certain. If those
tests pass, then I will post a patch that modifies
hpcd_quirk_uli5288().
So please, don't revert any patches. And thanks to everyone for
helping me resolve this issue.
--=20
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2009-04-16 21:28 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
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 [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=ed82fe3e0904161427y4d4e7f4ewcf39956ab82d4de9@mail.gmail.com \
--to=timur@freescale.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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).