From: Jeff Garzik <jgarzik@pobox.com>
To: Randy Dunlap <randy_d_dunlap@linux.intel.com>
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
axboe@suse.de, hch@lst.de
Subject: Re: [PATCH/RFC] SCSI mid-layer suspend/resume
Date: Tue, 25 Oct 2005 17:37:47 -0400 [thread overview]
Message-ID: <435EA5AB.9010805@pobox.com> (raw)
In-Reply-To: <20051025142529.7b23bbc0.randy_d_dunlap@linux.intel.com>
Randy Dunlap wrote:
> On Mon, 24 Oct 2005 19:29:11 -0400
> Jeff Garzik <jgarzik@pobox.com> wrote:
>
>
>>Randy Dunlap wrote:
>>
>>>Jeff's comments[2]:
>>>- Issue hardware or software reset on suspend (not done).
>>
>>Note that's an ATA-specific comment.
>
>
> So it is. Thanks for the reminder.
>
> How/where can I put low-level driver specific suspend/resume
> code, for PATA or SATA or usb-storage or ieee1394 or SCSI?
> What is the linkage (chain, pointers, whatever) thru the
> SCSI stack to each driver's "methods"? Or do those not
> exist yet?
Want the completely honest answer? :) I have no clue, and thinking
about suspend gives me a headache Anytime I start reading the actual
suspend code, I wind up either confused or depressed, or both.
We have emperical evidence that Jens' patch works on SATA, so see if the
two patches can meet in the middle somewhere?
Jeff
next prev parent reply other threads:[~2005-10-25 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 23:05 [PATCH/RFC] SCSI mid-layer suspend/resume Randy Dunlap
2005-10-24 23:29 ` Jeff Garzik
2005-10-25 21:25 ` Randy Dunlap
2005-10-25 21:37 ` Jeff Garzik [this message]
2005-10-27 3:35 ` Mark Lord
2005-10-27 9:17 ` Erik Slagter
2005-10-27 12:51 ` Mark Lord
2005-10-27 12:56 ` Mark Lord
2005-10-27 15:07 ` Erik Slagter
2005-10-26 4:26 ` Stefan Richter
2005-10-25 2:55 ` Mark Lord
2005-10-25 3:08 ` Mark Lord
2005-10-25 21:22 ` Randy Dunlap
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=435EA5AB.9010805@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=hch@lst.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy_d_dunlap@linux.intel.com \
/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).