linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: jeff@garzik.org, axboe@suse.de, htejun@gmail.com,
	jeremy@goop.org, lkml@rtr.ca, linux-ide@vger.kernel.org
Subject: Re: [PATCH 3/6] The definition of ahci_port_standby() and	ahci_port_spinup()
Date: Fri, 02 Jun 2006 10:14:57 +0200	[thread overview]
Message-ID: <447FF381.4060707@suse.de> (raw)
In-Reply-To: <1149234328.13451.56.camel@forrest26.sh.intel.com>

zhao, forrest wrote:
> Put port power management[1], staggered-spinup[2], cold presence
> detection[3] related operations during the power state transition into
> ahci_port_standby() and ahci_port_spinup().
> 
> In particular ahci_port_standby() does the [1] and [2] when power transits
> to a lower level; ahci_port_spinup() does [1], [2] and [3] when power
> transits to a higher level.
> 
Did you actually test with staggered-spinup and/or cold-presence
detection? I just added them per spec but never got a chance to test
them here.

And: it might be an idea to rename the HOST_CAP bits to be consistent
with those printed during initialisation. It's bad enough as it is (ie
the spec uses different abbrevs than the implementation), but we should
try to be consistent within the implementation.
I would rename them to HOST_CAP_STAG and HOST_CAP_SLUM.

Add slumber mode: libata-core used to issue a port reset with an
implicit SLUMBER/PARTIAL mode disable. So after a reset we might not be
able to put the device into SLUMBER mode even if supported.
What was the reasoning for this?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux Products GmbH		S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de

  reply	other threads:[~2006-06-02  8:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-02  7:45 [PATCH 3/6] The definition of ahci_port_standby() and ahci_port_spinup() zhao, forrest
2006-06-02  8:14 ` Hannes Reinecke [this message]
2006-06-02  9:01   ` zhao, forrest
2006-06-03 13:23 ` Tejun Heo
2006-06-03 19:16   ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2006-06-06 10:17 zhao, forrest
2006-06-29  8:19 zhao, forrest
2006-07-10  3:35 zhao, forrest
2006-07-11  6:38 zhao, forrest
2006-07-13  5:38 zhao, forrest

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=447FF381.4060707@suse.de \
    --to=hare@suse.de \
    --cc=axboe@suse.de \
    --cc=forrest.zhao@intel.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jeremy@goop.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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).