linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] libata: Add ALPM power state accounting to the AHCI driver
Date: Tue, 17 Nov 2009 00:40:13 +0900	[thread overview]
Message-ID: <4B01725D.3040204@kernel.org> (raw)
In-Reply-To: <4B017133.3060209@kernel.org>

Tejun Heo wrote:
> Hello, Arjan.
> 
> Arjan van de Ven wrote:
>> I think I'm waaaay out of my league in terms of understanding the
>> libata structure in the things you are suggesting to be honest, and I
>> do not feel I understand enough of the subtleties in this area.
> 
> SCR access is a bit subtle because it requires issuing commands if the
> link is behind PMP and internal commands currently assume EH context.
> This is true for all link functions, so I'm suggesting the stats
> helpers to follow the same convention.  This will also make slave link
> configuration work properly (controllers which present two SATA links
> as master/slave of the same port but still provide access to separate
> SCR registers).  You know, it's a link function, make it take a link
> as all other stuff is designed that way.

Oooh... right, I missed that part about exporting to sysfs.  It won't
show up properly for slave links anyway.  Sorry to keep nagging but
it's quite uncomfortable for me to see the code go in as-is.  ALPM was
one thing as it was host specific feature anyway but this is a clearly
link level thing being implemented at the port layer.  Then again, I
agree there isn't any easy solution at this time.  So, I don't object
to the current implementation.

Argh...........

Thanks.

-- 
tejun

  reply	other threads:[~2009-11-16 15:40 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 [this message]
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
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=4B01725D.3040204@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.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).