From: Hannes Reinecke <hare@suse.de>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, Jens Axboe <axboe@suse.de>,
Mark Lord <lkml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: State of resume for AHCI?
Date: Fri, 02 Jun 2006 08:39:46 +0200 [thread overview]
Message-ID: <447FDD32.7070403@suse.de> (raw)
In-Reply-To: <1149210165.13451.4.camel@forrest26.sh.intel.com>
zhao, forrest wrote:
> On Thu, 2006-06-01 at 13:19 -0700, Jeremy Fitzhardinge wrote:
>> Jens Axboe wrote:
>>> 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.
>>>
>> Hannes Reinecke's patch implements those functions, basically by
>> factoring out the shutdown and init code and calling them at
>> suspend/resume time as well.
>>
>> Is that correct/sufficient? Or should something else be happening?
>
> According to our test of Hannes's patch, it's not sufficient to support
> AHCI suspend/resume.
>
> Now I'm writing a patch to try to provide complete support for AHCI
> suspend/resume and will send out patch soon, hopefully by the end of
> today.
>
Can I have details, please? What doesn't work?
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
next prev parent reply other threads:[~2006-06-02 6:39 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
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 [this message]
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=447FDD32.7070403@suse.de \
--to=hare@suse.de \
--cc=axboe@suse.de \
--cc=forrest.zhao@intel.com \
--cc=jeff@garzik.org \
--cc=jeremy@goop.org \
--cc=linux-ide@vger.kernel.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 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.