From: Jeff Garzik <jgarzik@pobox.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] libata: Add ALPM power state accounting to the AHCI driver
Date: Mon, 16 Nov 2009 16:21:26 -0500 [thread overview]
Message-ID: <4B01C256.1070502@pobox.com> (raw)
In-Reply-To: <20091116064308.741b9a5b@infradead.org>
On 11/16/2009 09:43 AM, Arjan van de Ven wrote:
> is there a hardware way to ask for the link status via a link level
> thing? I thought the sata_scr_read() was by definition a host thing
It is by definition a link-level thing, which is why sata_scr_read()
takes struct ata_link * as its first argument.
Think about it... a port multiplier has downstream links, each with
their own link status, and link-related statistics.
Jeff
next prev parent reply other threads:[~2009-11-16 21:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 3:24 [PATCH] libata: Add ALPM power state accounting to the AHCI driver Arjan van de Ven
2009-11-15 8:05 ` Tejun Heo
2009-11-15 8:27 ` Jeff Garzik
2009-11-15 17:46 ` Arjan van de Ven
2009-11-15 18:06 ` Tejun Heo
2009-11-15 18:23 ` Arjan van de Ven
2009-11-15 18:26 ` Tejun Heo
2009-11-15 18:33 ` Arjan van de Ven
2009-11-16 1:51 ` Tejun Heo
2009-11-16 2:00 ` Arjan van de Ven
2009-11-16 2:15 ` Tejun Heo
2009-11-16 5:55 ` Arjan van de Ven
2009-11-16 6:14 ` Tejun Heo
2009-11-16 8:13 ` Jeff Garzik
2009-11-16 14:43 ` Arjan van de Ven
2009-11-16 14:59 ` Tejun Heo
2009-11-16 15:21 ` Arjan van de Ven
2009-11-16 15:35 ` Tejun Heo
2009-11-16 15:40 ` Tejun Heo
2009-11-16 15:57 ` Alan Cox
2009-11-16 16:25 ` Tejun Heo
2009-11-16 21:25 ` Jeff Garzik
2009-11-16 21:21 ` Jeff Garzik [this message]
2009-11-17 5:25 ` Arjan van de Ven
2009-11-15 17:00 ` Arjan van de Ven
2009-11-15 18:36 ` Arjan van de Ven
2009-11-15 18:42 ` Arjan van de Ven
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=4B01C256.1070502@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.