From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
jslaby@suse.cz, cwillu@cwillu.com, jackdachef@gmail.com
Subject: Re: [PATCH] libata: disable runtime pm for hotpluggable port
Date: Mon, 12 Mar 2012 14:29:49 +0400 [thread overview]
Message-ID: <4F5DD01D.3010609@mvista.com> (raw)
In-Reply-To: <1331515012.3412.37.camel@minggr>
Hello.
On 12-03-2012 5:16, Lin Ming wrote:
> Currently, hotplug doesn't work if port is already runtime suspended.
> For now, we simply disable runtime pm for hotpluggable port.
> Later, we should add runtime pm support for hotpluggable port too.
> https://lkml.org/lkml/2012/2/19/70
> TODO: add similar hotpluggable port check for controllers other than AHCI.
> Reported-and-tested-by: Jiri Slaby<jslaby@suse.cz>
> Reported-and-tested-by: cwillu@cwillu.com
> Reported-and-tested-by: jackdachef@gmail.com
> Signed-off-by: Lin Ming<ming.m.lin@intel.com>
[...]
> diff --git a/include/linux/libata.h b/include/linux/libata.h
> index 3085bdc..ccf0282 100644
> --- a/include/linux/libata.h
> +++ b/include/linux/libata.h
> @@ -209,8 +209,10 @@ enum {
> ATA_FLAG_SW_ACTIVITY = (1<< 22), /* driver supports sw activity
> * led */
> ATA_FLAG_NO_DIPM = (1<< 23), /* host not happy with DIPM */
> + ATA_FLAG_EXTERNAL = (1<< 24), /* controller supports external SATA */
> + ATA_FLAG_PLUGGABLE = (1<< 25), /* port is hotpluggable */
>
> - /* bits 24:31 of ap->flags are reserved for LLD specific flags */
> + /* bits 26:31 of ap->flags are reserved for LLD specific flags */
There's no need to use bits 24..25, I've freed up some lower order bits
last year, removing unused values.
WBR, Sergei
next prev parent reply other threads:[~2012-03-12 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 1:16 [PATCH] libata: disable runtime pm for hotpluggable port Lin Ming
2012-03-12 10:29 ` Sergei Shtylyov [this message]
2012-03-12 11:59 ` Lin Ming
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=4F5DD01D.3010609@mvista.com \
--to=sshtylyov@mvista.com \
--cc=cwillu@cwillu.com \
--cc=jackdachef@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jslaby@suse.cz \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
/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