All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Tim Small <tim@buttersideup.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: AHCI link power management and surprise hotplug
Date: Fri, 20 Mar 2009 10:42:57 -0700	[thread overview]
Message-ID: <20090320104257.5cf1e7cc@appleyard> (raw)
In-Reply-To: <49C22689.9050005@buttersideup.com>

On Thu, 19 Mar 2009 04:03:37 -0700
Tim Small <tim@buttersideup.com> wrote:

> Hello,
> 
> I've been configuring SATA link power management
> (Documentation/scsi/link_power_management_policy.txt) on servers which
> use software RAID for a while, but I happened to come across this in the
> ICH9 datasheet:
> 
> "
> For reliable device removal notification while in AHCI operation without
> the use of interlock switches (surprise removal), interface power
> management should be disabled for the associated port. See Section 7.3.1
> of the AHCI Specification for more information.
> "
> 
> 
> Is this actually an issue from a libata point of view?  Do I need to
> ensure that link power management is disabled prior to hot-removal, and
> if so, I suppose link_power_management_policy.txt should be updated to
> reflect this...

Hi,
Yes - this is an issue.  Right now we disable hotplug when link power
management is enabled because when your link is in a lower power state
it cannot detect the phy state changes.  Most platforms I've seen do
not support the interlock switches - so ATM link pwr management and 
hotplug are mutually excludive.  I agree that the documentation
should reflect this - would you like to submit a patch to the
link_power_management_policy.txt file?

Thanks!
Kristen

      parent reply	other threads:[~2009-03-20 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 11:03 AHCI link power management and surprise hotplug Tim Small
2009-03-19 18:06 ` Jeff Garzik
2009-03-20  1:56 ` Tejun Heo
2009-03-20 17:42 ` Kristen Carlson Accardi [this message]

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=20090320104257.5cf1e7cc@appleyard \
    --to=kristen.c.accardi@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=tim@buttersideup.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 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.