From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
Jens Axboe <axboe@suse.de>,
linux-ide@vger.kernel.org
Cc: "Wichert, Gerhard" <Gerhard.Wichert@fujitsu-siemens.com>
Subject: ahci, SActive flag, and the HD activity LED
Date: Tue, 02 Aug 2005 17:40:40 +0200 [thread overview]
Message-ID: <42EF93F8.8050601@fujitsu-siemens.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Hello Jeff, hello Jens, hello everybody,
I am referring to the debate about whether or not setting the SActive
bit for non-NCQ ATA commands (e.g. http://lkml.org/lkml/2005/5/26/142).
In our machines, this behavior of the Linux AHCI driver causes the HD
activity LED to stay on all the time. If I apply the attached trivial
patch (this is for the RedHat EL4.0-U1 kernel), the LED behaves nicely.
Jeff has stated in the above thread that "SActive is intentionally used
for non-NCQ devices". However I find clear indication in the specs that
the SActive flag should be set if and only if tagged queuing is being
used, and only for a specified subset of commands that support queuing
(http://www.t13.org/docs2005/D1699r1e-ATA8-ACS.pdf, secs. 4.19 and
4.20). The current mainline driver doesn't use queuing.
If I am reading the specs correctly, that'd mean the ahci driver is
wrong in setting the SActive bit. Could you please comment? Jeff, in
particular, could you please give more detail why you say this flag is
"intentionally used"?
Regards
Martin
--
Martin Wilck Phone: +49 5251 8 15113
Fujitsu Siemens Computers Fax: +49 5251 8 20409
Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com
D-33106 Paderborn http://www.fujitsu-siemens.com/primergy
[-- Attachment #2: ahci_sactive.diff --]
[-- Type: text/x-patch, Size: 383 bytes --]
--- ahci.c.orig 2005-06-13 11:39:26.000000000 +0200
+++ ahci.c 2005-08-02 10:48:47.000000000 +0200
@@ -691,9 +703,6 @@
struct ata_port *ap = qc->ap;
void *port_mmio = (void *) ap->ioaddr.cmd_addr;
- writel(1, port_mmio + PORT_SCR_ACT);
- readl(port_mmio + PORT_SCR_ACT); /* flush */
-
writel(1, port_mmio + PORT_CMD_ISSUE);
readl(port_mmio + PORT_CMD_ISSUE); /* flush */
next reply other threads:[~2005-08-02 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 15:40 Martin Wilck [this message]
2005-08-02 16:35 ` ahci, SActive flag, and the HD activity LED Jens Axboe
2005-08-03 5:17 ` Martin Wilck
2005-08-03 6:19 ` Jens Axboe
2005-08-04 23:49 ` Eric D. Mudama
2005-08-03 6:41 ` Pasi Kärkkäinen
2005-08-03 11:08 ` André Tomt
2005-08-03 18:12 ` Adam Goode
2005-08-04 7:04 ` [PATCH] Fix HD activity LED with ahci Martin Wilck
2005-08-22 4:35 ` Jeff Garzik
2005-08-26 12:59 ` Martin Wilck
2005-08-23 5:03 ` Jeff Garzik
2005-08-03 19:21 ` ahci, SActive flag, and the HD activity LED Matthias Schniedermeyer
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=42EF93F8.8050601@fujitsu-siemens.com \
--to=martin.wilck@fujitsu-siemens.com \
--cc=Gerhard.Wichert@fujitsu-siemens.com \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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