linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, flyboy@gmail.com
Subject: Re: [PATCH] ahci: do not powerdown during initialization
Date: Wed, 29 Nov 2006 12:52:00 +0900	[thread overview]
Message-ID: <456D03E0.1080805@gmail.com> (raw)
In-Reply-To: <456BFE30.2010602@pobox.com>

Jeff Garzik wrote:
> Tejun Heo wrote:
>> ahci_init_controller() calls ahci_deinit_port() to make sure the
>> controller is stopped before initializing the controller.  In turn,
>> ahci_deinit_port() invokes ahci_power_down() to power down the port.
>> If the controller supports slumber mode, the link is put into it.
> 
> I would rather just pass a 'dont suspend port' flag to 
> ahci_deinit_port().  That leaves ahci_port_stop() behavior unchanged.

That behavior change is intended.  ahci_port_stop() must not call 
ahci_power_down(); otherwise, it will cause strange behaviors on some 
devices on driver unloading.

The baseline is that power up/down shouldn't be done as part of 
controller init/deinit.  Power up/down involves link power management 
operation which make some devices choke.  They should only be done when 
actual power management is required.  This is okay even for devices 
which choke on link pm because system-wide PM powers those devices down 
clearing lockup.  I dunno what should be done with partial power 
management tho.

-- 
tejun

      reply	other threads:[~2006-11-29  3:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20  6:42 [PATCH] ahci: do not powerdown during initialization Tejun Heo
2006-11-24 17:53 ` Berck E. Nash
2006-11-28  9:15 ` Jeff Garzik
2006-11-29  3:52   ` Tejun Heo [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=456D03E0.1080805@gmail.com \
    --to=htejun@gmail.com \
    --cc=flyboy@gmail.com \
    --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).