Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753292AbbETIlg (ORCPT ); Wed, 20 May 2015 04:41:36 -0400 Received: from cantor2.suse.de ([195.135.220.15]:52676 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751682AbbETIl2 (ORCPT ); Wed, 20 May 2015 04:41:28 -0400 Message-ID: <1432111237.8287.3.camel@suse.com> Subject: Re: [RESEND][PATCH] Bluetooth: Make request workqueue freezable From: Oliver Neukum To: Takashi Iwai Cc: Ming Lei , "David S. Miller" , Laura Abbott , Johan Hedberg , Marcel Holtmann , "Rafael J. Wysocki" , "Gustavo F. Padovan" , Laura Abbott , Alan Stern , "bluez mailin list (linux-bluetooth@vger.kernel.org)" , Linux Kernel Mailing List , linux-usb@vger.kernel.org, netdev Date: Wed, 20 May 2015 10:40:37 +0200 In-Reply-To: References: <1432057375.3970.4.camel@suse.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 817 Lines: 21 On Wed, 2015-05-20 at 08:29 +0200, Takashi Iwai wrote: > The data is cached in RAM. More specifically, the former loaded > firmware files are reloaded and saved at suspend for each device > object. See fw_pm_notify() in firmware_class.c. OK, this may be a stupid idea, but do we know the firmware was successfully loaded in the first place? Also btusb is in the habit of falling back to a generic firmware in some places. It seems to me that caching firmware is conceptually not enough, but we'd also need to record the absence of firmware images. Regards Oliver -- 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/