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-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
