From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [PATCH/RFC] SCSI mid-layer suspend/resume Date: Tue, 25 Oct 2005 17:37:47 -0400 Message-ID: <435EA5AB.9010805@pobox.com> References: <20051024160531.7d879a7c.randy_d_dunlap@linux.intel.com> <435D6E47.1030409@pobox.com> <20051025142529.7b23bbc0.randy_d_dunlap@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051025142529.7b23bbc0.randy_d_dunlap@linux.intel.com> Sender: linux-ide-owner@vger.kernel.org To: Randy Dunlap Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org, axboe@suse.de, hch@lst.de List-Id: linux-scsi@vger.kernel.org Randy Dunlap wrote: > On Mon, 24 Oct 2005 19:29:11 -0400 > Jeff Garzik 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