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: Mon, 16 Nov 2009 15:14:04 +0900 [thread overview]
Message-ID: <4B00EDAC.4080904@kernel.org> (raw)
In-Reply-To: <20091115215531.23edcf5e@infradead.org>
Hello,
Arjan van de Ven wrote:
> sigh. so I moved all the generic logic generic, and left the ahci
> specific code specific to ahci. I put the logic there where it was
> easy to implement, and there where the other link power management
> controls are (in sysfs). If that's not good enough, I'm out of my skills
> in the libata world to be honest, and would like to ask you to implement
> that instead. let me know what sysfs looks like and I'll adjust
> powertop to it....
The reason why we have sysfs attributes which should have been at link
layer at host was that it originally was for ahci alpm which is host
specific feature which got extended to something somewhat generic.
Now another pm feature which should belong to link is added to host
following the precedence.
Then again, it's also true that nobody really cares about ATA PM
features enough during past couple of years so I really don't want to
prevent the feature you're trying to add. It would be best if there's
someone who would pick it up and implement proper infrastructure but
well that doesn't seem to be happening anytime soon.
So, I don't know. That's the concern I have but I don't want to nack
your change either. One thing is at least make those functions take
ata_link isntead of ata_port as there's nothing port specific about
those. Jeff, what do you think?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-11-16 6:14 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 [this message]
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
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=4B00EDAC.4080904@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 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.