linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	randy_d_dunlap@linux.intel.com, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	acpi-devel@lists.sourceforge.net
Subject: Re: RFC: ACPI/scsi/libata integration and hotswap
Date: Thu, 08 Dec 2005 14:01:38 +0000	[thread overview]
Message-ID: <1134050498.17102.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20051208133945.GA21633@srcf.ucam.org>

On Iau, 2005-12-08 at 13:39 +0000, Matthew Garrett wrote:
> On Thu, Dec 08, 2005 at 01:33:08PM +0000, Christoph Hellwig wrote:
> 
> > Don't do it at all.  We don't need to fuck up every layer and driver for
> > intels braindamage.
> 
> Doing SATA suspend/resume properly on x86 depends on knowing the ACPI 
> object that corresponds to a host or target. It's also the only way to 
> support hotswap on this hardware[1], since there's no way for userspace 
> to know which device a notification refers to.
> 
> [1] ie, most laptops sold nowadays

Actually "most PC systems"

Nevertheless Christoph has a point even if its hidden behind a George
Bush approach to diplomacy. The scsi core directly shouldn't need to
know about ACPI or other arch specific PM systems. 

Something like  "pci_to_acpi(struct pcidev *)" belongs in arch specific
code even if we do add a generic "void * pm_device" type pointer to
struct pci_dev or struct device for such a purpose.

Alan


  parent reply	other threads:[~2005-12-08 14:03 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08  3:02 RFC: ACPI/scsi/libata integration and hotswap Matthew Garrett
2005-12-08  9:15 ` Christoph Hellwig
2005-12-08 13:26   ` Matthew Garrett
2005-12-08 13:33     ` Christoph Hellwig
2005-12-08 13:39       ` Matthew Garrett
2005-12-08 13:44         ` Christoph Hellwig
2005-12-08 17:18           ` Erik Slagter
2005-12-08 20:43             ` Jeff Garzik
2005-12-08 21:03               ` Dominic Ijichi
2005-12-08 21:09                 ` Jeff Garzik
2005-12-08 21:34                   ` Dominic Ijichi
2005-12-08 21:31               ` Randy Dunlap
2005-12-09  9:45                 ` Erik Slagter
2005-12-09 10:39                   ` Jens Axboe
2005-12-09 10:45                     ` Erik Slagter
2005-12-09 11:27                       ` Jeff Garzik
2005-12-09 11:35                         ` Erik Slagter
2005-12-09 11:40                           ` Christoph Hellwig
2005-12-09 11:46                           ` Jens Axboe
2005-12-09 11:55                             ` Matthew Garrett
2005-12-09 13:22                               ` Bartlomiej Zolnierkiewicz
2005-12-09 12:01                             ` Erik Slagter
2005-12-09 12:07                               ` Jens Axboe
2005-12-10  2:19                         ` Douglas Gilbert
2005-12-14 20:52                           ` [ACPI] " Matthew Wilcox
2005-12-09 11:30                       ` Jens Axboe
2005-12-09  3:28               ` Mark Lord
2005-12-09 11:29                 ` Jeff Garzik
2005-12-10  4:01                   ` Mark Lord
2005-12-08 13:52         ` Jeff Garzik
2005-12-08 14:07           ` [ACPI] " Alan Cox
2005-12-08 14:14             ` Jeff Garzik
2005-12-08 14:30               ` Alan Cox
2005-12-08 14:43                 ` Matthew Garrett
2005-12-08 14:53                   ` Alan Cox
2005-12-09 11:42                 ` Jeff Garzik
2005-12-08 14:12           ` Matthew Garrett
2005-12-08 14:01         ` Alan Cox [this message]
2005-12-08 14:18           ` Matthew Garrett
2005-12-08 14:33             ` Alan Cox
2005-12-08 14:52               ` Matthew Garrett
2005-12-08 14:55                 ` Alan Cox
2005-12-08 17:19                 ` Matthew Garrett
2005-12-09 11:42                   ` Christoph Hellwig
2005-12-09 11:49                     ` Jeff Garzik
2005-12-09 11:52                       ` Matthew Garrett
2005-12-09 11:58                         ` Jeff Garzik
2005-12-09 12:11                           ` Matthew Garrett
2005-12-09 12:16                             ` Jeff Garzik
2005-12-09 12:24                               ` Matthew Garrett
2005-12-10  0:40                                 ` Jeff Garzik
2005-12-10  2:34                                   ` Matthew Garrett
2005-12-10  2:39                                     ` Jeff Garzik
2005-12-10  2:47                                       ` Matthew Garrett
2005-12-10  2:41                                     ` Jeff Garzik
2005-12-10  2:50                                       ` Matthew Garrett
2005-12-10  2:57                                         ` Jeff Garzik
2005-12-10  3:47                                           ` [ACPI] " Andrew Grover
2005-12-12  0:38                                       ` Alan Cox
2005-12-09 11:50                     ` Matthew Garrett
2005-12-09 11:55                       ` Christoph Hellwig
2005-12-13 18:14 ` Randy Dunlap
2005-12-13 18:26   ` Matthew Garrett
2005-12-13 19:07     ` Randy Dunlap
2005-12-08 13:57 Salyzyn, Mark

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=1134050498.17102.2.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=hch@infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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).