From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: libata hotplug question Date: Tue, 01 Dec 2009 16:30:09 +1100 Message-ID: <1259645409.2076.213.camel@pasglop> References: <1259561052.2076.73.camel@pasglop> <1259624651.2076.158.camel@pasglop> <4B1459B5.40504@kernel.org> <1259635420.2076.180.camel@pasglop> <1259644647.2076.204.camel@pasglop> <4B14A809.8000304@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from gate.crashing.org ([63.228.1.57]:52969 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752557AbZLAFao (ORCPT ); Tue, 1 Dec 2009 00:30:44 -0500 In-Reply-To: <4B14A809.8000304@kernel.org> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tejun Heo Cc: linux-ide@vger.kernel.org On Tue, 2009-12-01 at 14:22 +0900, Tejun Heo wrote: > Hello, > > On 12/01/2009 02:17 PM, Benjamin Herrenschmidt wrote: > > So I tried with implementing the link_online and link_offline callbacks > > and it doesn't fly very high. > > > > When I unplug the bay, it displays: > > > > ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen > > ata3: EH complete > > You didn't schedule any EH actions, right? I did the usual ehi_hotplug + freeze > libata-acpi.c does that. Setting ATA_DFLAG_DETACH device flag and > scheduling EH will do that. Please take a look at > ata_acpi_detach_device() but you must be *sure* that your hot unplug > notification is completely reliable. Well, it seems to be reliable that way for unplugs. I even debounce it both ways but I'm actually considering removing the debounce on unplug. I'll let you know how it goes with a custom prereset() that returns -ENODEV. How would that differ from ATA_DFLAG_DETACH ? Cheers, Ben.