From: Jarno Paananen <jpaana@s2.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Promise 579 with current(?) libata in libata-dev-2.6 queue
Date: Tue, 19 Oct 2004 03:40:51 +0300 [thread overview]
Message-ID: <m36557k0a4.fsf@kalahari.s2.org> (raw)
In-Reply-To: <417023B6.9070900@pobox.com> (Jeff Garzik's message of "Fri, 15 Oct 2004 15:23:34 -0400")
Jeff Garzik <jgarzik@pobox.com> writes:
> There are additional interrupt events on the new cards that
> sata_promise doesn't know about. Ack or disable those events, and
> things should work.
>
> Jeff
Thanks,
it seems the comment:
/* reading should also clear interrupts */
doesn't hold for the 579, but some reading of the Promise driver
and adding a simple
writel(mask, mmio_base + PDC_INT_SEQMASK);
after the spin_lock (didn't know which side it should be, the but
the Promise driver does it after checking the 0xffff, and after the
spinlock seemed safe :) makes the driver work nicely for me. Dunno
if this is safe for other controllers than the 579 though, so it
might be useful to define a new card type for it.
// Jarno
--- sata_promise.c.old 2004-10-19 03:38:55.000000000 +0300
+++ sata_promise.c 2004-10-19 03:32:33.000000000 +0300
@@ -158,6 +158,8 @@
board_2037x },
{ PCI_VENDOR_ID_PROMISE, 0x3376, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
board_2037x },
+ { PCI_VENDOR_ID_PROMISE, 0x3574, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+ board_2037x },
{ PCI_VENDOR_ID_PROMISE, 0x3318, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
board_20319 },
{ PCI_VENDOR_ID_PROMISE, 0x3319, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
@@ -438,6 +440,8 @@
spin_lock(&host_set->lock);
+ writel(mask, mmio_base + PDC_INT_SEQMASK);
+
for (i = 0; i < host_set->n_ports; i++) {
VPRINTK("port %u\n", i);
ap = host_set->ports[i];
next prev parent reply other threads:[~2004-10-19 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 16:22 Promise 579 with current(?) libata in libata-dev-2.6 queue Jarno Paananen
2004-10-15 19:23 ` Jeff Garzik
2004-10-19 0:40 ` Jarno Paananen [this message]
2005-02-06 2:54 ` Jeff Garzik
2004-10-25 17:56 ` Jarno Paananen
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=m36557k0a4.fsf@kalahari.s2.org \
--to=jpaana@s2.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.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).