linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: acpi-support@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Supporting ACPI drive hotswap
Date: Sat, 24 Sep 2005 17:48:23 +0100	[thread overview]
Message-ID: <20050924164823.GA24351@srcf.ucam.org> (raw)

ACPI provides a mechanism for noting which devices can be hotswapped and 
notifying the system that this has happened. Hotswappable devices are 
tagged with a _RMV token. What effectively needs to be done is this:

1) Find every device with an _RMV token, and install a notify handler 
for it. This is fairly easy.

2) On notification, check whether the device is present or absent. This 
can be done by calling the _STA method - alternatively it could 
presumably be done through the appropriate IDE or SCSI layer. I believe 
that we now have code that allows binding of ACPI devices to appropriate 
busses.

3) If a device has been added, enumerate it and do appropriate messaging
to userspace (for device node creation and so forth). This ought to be 
relatively easy?

4) If a device has been removed, we currently have problems. SATA 
hotplugging is only supported on a subset of devices. The SATA laptop I 
have here is an Intel ICH part, but uses the ata_piix driver (ahci won't 
load) which isn't supposed to support hotswap. Unregistering devices in 
the IDE layer has been broken for ages.

Is there any point in working on the first three of these points until 
point four is more reasonable? What actually needs to be done to improve 
this?
-- 
Matthew Garrett | mjg59@srcf.ucam.org

             reply	other threads:[~2005-09-24 16:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 16:48 Matthew Garrett [this message]
2005-09-24 19:40 ` Supporting ACPI drive hotswap Randy.Dunlap
2005-09-24 19:45   ` Mark Lord
2005-09-24 21:14     ` Matthew Garrett

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=20050924164823.GA24351@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=acpi-support@lists.sourceforge.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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).