Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261219AbTEQEkj (ORCPT ); Sat, 17 May 2003 00:40:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261220AbTEQEkj (ORCPT ); Sat, 17 May 2003 00:40:39 -0400 Received: from dp.samba.org ([66.70.73.150]:53457 "EHLO lists.samba.org") by vger.kernel.org with ESMTP id S261219AbTEQEkg (ORCPT ); Sat, 17 May 2003 00:40:36 -0400 Date: Sat, 17 May 2003 14:50:08 +1000 From: David Gibson To: Oliver Neukum Cc: Alan Cox , ranty@debian.org, LKML , Simon Kelley , "Downing, Thomas" , Greg KH , jt@hpl.hp.com, Pavel Roskin Subject: Re: request_firmware() hotplug interface, third round. Message-ID: <20030517045008.GD13827@zax> Mail-Followup-To: David Gibson , Oliver Neukum , Alan Cox , ranty@debian.org, LKML , Simon Kelley , "Downing, Thomas" , Greg KH , jt@hpl.hp.com, Pavel Roskin References: <1053101342.5589.5.camel@dhcp22.swansea.linux.org.uk> <200305170013.49808.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305170013.49808.oliver@neukum.org> User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1629 Lines: 34 On Sat, May 17, 2003 at 12:13:49AM +0200, Oliver Neukum wrote: > Am Freitag, 16. Mai 2003 18:09 schrieb Alan Cox: > > On Gwe, 2003-05-16 at 09:07, Oliver Neukum wrote: > > > So, if I understand you correctly, RAM is only saved if a device > > > is hotpluggable and needs firmware only upon intial connection. > > > Which, if you do suspend to disk correctly, is no device. > > > > Thats just because the interface is a little warped not the theory. > > On a resume you need to reload firmware and you already handle > > rediscovery on USB bus for example because the devices can change > > Right. But the order of resumption is fixed by hardware needs. > So during resumption you cannot use block devices and therefore > not start a hotplug script. Or did I miss something? For devices that aren't essentialy to get userspace running (e.g. network on a laptop running from local disk), the firmware request doesn't have to happen during the hairy part of resumption. The device could just mark itself as unusable at suspend time, then at resume it schedule_work()s something to reload the firmware and complete reinitialization. Shortly after userspace is back in action, the device will come back to life. -- David Gibson | For every complex problem there is a david@gibson.dropbear.id.au | solution which is simple, neat and | wrong. http://www.ozlabs.org/people/dgibson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/