linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: tj@kernel.org, linux-ide@vger.kernel.org
Subject: "ahci: drop intx manipulation on msi enable" breaks ULI M1575
Date: Tue, 07 Apr 2009 09:54:12 -0500	[thread overview]
Message-ID: <49DB6914.1030107@freescale.com> (raw)

Tejun,

Your patch

> 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:

ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed
irq 19
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: limiting SATA link speed to 1.5 Gbps
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

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.

-- 
Timur Tabi
Linux kernel developer at Freescale

             reply	other threads:[~2009-04-07 14:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 14:54 Timur Tabi [this message]
2009-04-07 23:57 ` "ahci: drop intx manipulation on msi enable" breaks ULI M1575 Tejun Heo
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=49DB6914.1030107@freescale.com \
    --to=timur@freescale.com \
    --cc=linux-ide@vger.kernel.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).