From: Jens Axboe <axboe@suse.de>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
ide <linux-ide@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
jgarzik <jgarzik@pobox.com>
Subject: Re: [PATCH 1/4] SATA ACPI build (applies to 2.6.16-git9)
Date: Mon, 16 Jan 2006 23:46:27 +0100 [thread overview]
Message-ID: <20060116224626.GS3945@suse.de> (raw)
In-Reply-To: <20060116140713.GB18307@harddisk-recovery.com>
On Mon, Jan 16 2006, Erik Mouw wrote:
> On Mon, Jan 16, 2006 at 12:56:07PM +0100, Erik Mouw wrote:
> > On Fri, Jan 13, 2006 at 10:42:52PM -0800, Randy.Dunlap wrote:
> > > --- linux-2615-g9.orig/drivers/scsi/Kconfig
> > > +++ linux-2615-g9/drivers/scsi/Kconfig
> > > @@ -599,6 +599,11 @@ config SCSI_SATA_INTEL_COMBINED
> > > depends on IDE=y && !BLK_DEV_IDE_SATA && (SCSI_SATA_AHCI || SCSI_ATA_PIIX)
> > > default y
> > >
> > > +config SCSI_SATA_ACPI
> > > + bool
> > > + depends on SCSI_SATA && ACPI
> > > + default y
> > > +
> >
> > Could you add some help text over here? At first glance I got the
> > impression this was a host driver that works through ACPI calls, but by
> > reading the rest of your patches it turns out it is a suspend/resume
> > helper.
>
> Something like this should already be enough:
>
> This option enables support for SATA suspend/resume using ACPI.
>
> If you really need this enabled to be able to use suspend/resume at
> all, you could add a line like:
>
> It's safe to say Y. If you say N, you might get serious disk
> corruption when you suspend your machine.
That's simply not true. If you say N (if you could), you could risk
having a non-responsive disk after resume. However, it would have been
synced a suspend time so you wont corrupt anything.
Maybe you don't know what the patch actually does. The main
suspend/resume support is in libata, all this adds is the ability to
retrieve the taskfiles that the BIOS/acpi thinks should be issued on
resume. That may be things like security unlocking the drive. There are
no data consistency issues involved.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-16 22:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 6:42 [PATCH 1/4] SATA ACPI build (applies to 2.6.16-git9) Randy.Dunlap
2006-01-14 6:44 ` [PATCH 2/4] libata debugging support Randy.Dunlap
2006-01-14 6:45 ` [PATCH 3/4] SATA ACPI objects support Randy.Dunlap
2006-01-14 6:45 ` [PATCH 4/4] additional libata parameters Randy.Dunlap
2006-01-18 0:35 ` [PATCH 2/4] libata debugging support Jeff Garzik
2006-01-14 7:28 ` [PATCH 1/4] SATA ACPI build (applies to 2.6.16-git9) Sam Ravnborg
2006-01-14 7:30 ` Randy.Dunlap
2006-01-16 11:56 ` Erik Mouw
2006-01-16 14:07 ` Erik Mouw
2006-01-16 21:04 ` Adrian Bunk
2006-01-17 9:01 ` Erik Mouw
2006-01-17 11:27 ` Adrian Bunk
2006-01-16 22:46 ` Jens Axboe [this message]
2006-01-16 22:48 ` Randy.Dunlap
2006-01-16 23:00 ` Alan Cox
2006-01-16 23:10 ` Jens Axboe
2006-01-18 12:24 ` Pavel Machek
2006-01-17 9:09 ` Erik Mouw
2006-01-16 15:40 ` Randy.Dunlap
2006-01-16 12:31 ` Jens Axboe
2006-01-16 15:37 ` Randy.Dunlap
2006-01-16 15:44 ` Jens Axboe
2006-01-16 15:51 ` Alan Cox
2006-01-16 15:52 ` Jens Axboe
2006-01-16 15:58 ` Randy.Dunlap
2006-01-16 16:02 ` Jens Axboe
2006-01-16 16:08 ` Randy.Dunlap
2006-01-16 22:43 ` Jens Axboe
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=20060116224626.GS3945@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=erik@harddisk-recovery.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).