public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Jeff Garzik <jeff@garzik.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: State of resume for AHCI?
Date: Thu, 1 Jun 2006 20:39:06 +0200	[thread overview]
Message-ID: <20060601183904.GR4400@suse.de> (raw)
In-Reply-To: <447F3250.5070101@rtr.ca>

On Thu, Jun 01 2006, Mark Lord wrote:
> The one-line "resume fix" (attached) *might* be all that you need.
> This is in current Linus 2.6.17-rc*-git*

It's a lot more complicated than that, I'm afraid. ahci doesn't even
have the resume/suspend methods defined, plus it needs more work than
piix on resume.

libata should define a default suspend hook for devices that haven't
added their own, to prevent accidents with people trying to suspend
devices that haven't been fixed up. It's a data integrity issue!

-- 
Jens Axboe


  reply	other threads:[~2006-06-01 18:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 17:28 State of resume for AHCI? Jeremy Fitzhardinge
2006-06-01 18:30 ` Mark Lord
2006-06-01 18:39   ` Jens Axboe [this message]
2006-06-01 20:19     ` Jeremy Fitzhardinge
2006-06-02  1:02       ` zhao, forrest
2006-06-02  3:39         ` Jeremy Fitzhardinge
2006-06-02  6:39         ` Hannes Reinecke
2006-06-02  6:03       ` Jens Axboe
2006-06-02  6:03         ` zhao, forrest
2006-06-02  6:41           ` Jens Axboe
2006-06-02  6:43             ` Hannes Reinecke
2006-06-02  6:49               ` zhao, forrest
2006-06-02  7:06                 ` Jens Axboe
2006-06-02  6:52               ` Jens Axboe
2006-06-01 18:48   ` Mark Lord
2006-06-06  2:16     ` Tejun Heo

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=20060601183904.GR4400@suse.de \
    --to=axboe@suse.de \
    --cc=jeff@garzik.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@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