From: Jeff Garzik <jeff@garzik.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-ide@vger.kernel.org, linux-acpi@vger.kernel.org,
Tejun Heo <htejun@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] libata: Integrate ACPI-based PATA/SATA hotplug - version 2
Date: Thu, 20 Sep 2007 18:04:22 -0400 [thread overview]
Message-ID: <46F2EE66.9060207@garzik.org> (raw)
In-Reply-To: <20070915170652.GA25504@srcf.ucam.org>
Matthew Garrett wrote:
> Modern laptops with hotswap bays still tend to utilise a PATA interface
> on a SATA bridge, generally with the host controller in some legacy
> emulation mode rather than AHCI. This means that the existing hotplug
> code in libata is unable to work. The ACPI specification states that
> these devices can send notifications when hotswapped, which avoids the
> need to obtain notification from the controller. This patch uses the
> existing libata-acpi code and simply registers a notification in order
> to trigger a rescan whenever the firmware signals an event.
>
> Signed-off-by: Matthew Garrett <mjg59@srcf.ucam.org>
>
> ---
>
> Testing on an HP with the hotplug device as the slave on a PATA channel
> flagged a bug - the notification needs to be tied to the channel handle
> as well as the device ones. With this version, I can happily hotswap the
> HP device. It ends up sitting for a few seconds while failing to
> revalidate, but then recovers with everything working fine.
the code looks correct. I have one main reservation.
how can we be sure that this is active only where other hand-programmed
hotplug code is absent?
ACPI doesn't inherently know which of our controllers are already set up
to do hotplug, so it seems like there is a possibility of conflict if
both the firmware and the controller are chirping.
If we can quell my fears in that area, I'm ok with the change.
Jeff
next prev parent reply other threads:[~2007-09-20 22:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 3:01 [PATCH] libata: Integrate ACPI-based PATA/SATA hotplug Matthew Garrett
2007-09-15 17:06 ` [PATCH] libata: Integrate ACPI-based PATA/SATA hotplug - version 2 Matthew Garrett
2007-09-16 12:22 ` Tejun Heo
2007-09-20 22:04 ` Jeff Garzik [this message]
2007-09-20 22:21 ` Matthew Garrett
2007-09-21 2:35 ` Tejun Heo
2007-09-21 2:42 ` Matthew Garrett
2007-09-21 2:53 ` Tejun Heo
2007-09-21 2:57 ` Matthew Garrett
2007-09-21 3:08 ` Tejun Heo
2007-09-21 3:12 ` Matthew Garrett
2007-09-21 3:19 ` Tejun Heo
2007-09-24 23:14 ` [PATCH] libata: Integrate ACPI-based PATA/SATA hotplug - version 3 Matthew Garrett
2007-09-27 17:26 ` Kristen Carlson Accardi
2007-09-27 17:55 ` Matthew Garrett
2007-09-27 20:39 ` Henrique de Moraes Holschuh
2007-10-02 15:04 ` Jeff Garzik
2007-10-02 18:46 ` Matthew Garrett
2007-10-02 18:49 ` [PATCH] libata: Integrate ACPI-based PATA/SATA hotplug - version 4 Matthew Garrett
2007-10-02 18:55 ` Jeff Garzik
2007-10-02 20:38 ` Jeff Garzik
2007-10-02 20:42 ` Matthew Garrett
2007-10-02 21:20 ` Matthew Garrett
2007-10-02 21:23 ` Jeff Garzik
2007-10-03 0:24 ` [PATCH] libata: Integrate ACPI-based PATA/SATA hotplug - version 5 Matthew Garrett
2007-10-03 20:27 ` Jeff Garzik
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=46F2EE66.9060207@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=mjg59@srcf.ucam.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).