Re: [RESEND][PATCH] Bluetooth: Make request workqueue freezable

On Wed, May 20, 2015 at 4:40 PM, Oliver Neukum [off-list ref] wrote:

On Wed, 2015-05-20 at 08:29 +0200, Takashi Iwai wrote:

quoted

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?

Yes, the firmware loader records that as device resource.
In reality, there won't be lots of devices requiring firmware
in one running system, so the idea of caching for every
successful loading is workable.

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.

The caching can't cover the case which starts to load fw
during resume in the 1st time.

        Regards
                Oliver