Re: State of resume for AHCI?

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?

   J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: State of resume for AHCI?
    • From: Jens Axboe <[email protected]>
  • Re: State of resume for AHCI?
    • From: "zhao, forrest" <[email protected]>

• References:
  • State of resume for AHCI?
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: State of resume for AHCI?
    • From: Mark Lord <[email protected]>
  • Re: State of resume for AHCI?
    • From: Jens Axboe <[email protected]>

• Prev by Date: Re: [PATCH] cramfs corruption after BLKFLSBUF on loop device
• Next by Date: Re: [PATCH] cramfs corruption after BLKFLSBUF on loop device
• Previous by thread: Re: State of resume for AHCI?
• Next by thread: Re: State of resume for AHCI?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]