Re: btusb "firmware request while host is not available" at resume

From	Kai-Heng Feng <kai.heng.feng@canonical.com>
Newsgroups	linux.kernel
Subject	Re: btusb "firmware request while host is not available" at resume
Date	2017-10-02 10:40 +0200
Message-ID	<uw4qB-52e-1@gated-at.bofh.it> (permalink)
References	(6 earlier) <uoDbQ-84z-23@gated-at.bofh.it> <uoLM5-5ru-5@gated-at.bofh.it> <uoWet-3Az-5@gated-at.bofh.it> <up9Op-3SS-13@gated-at.bofh.it> <upjXr-1Yv-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi Luis,

On Thu, Sep 14, 2017 at 1:39 AM, Luis R. Rodriguez <mcgrof@kernel.org> wrote:
[snipped]
> Would a fw_cache_hint(device, name_list) be reasonable then sometime *before*
> suspend? All this would do is ask the firmware API to extend the fw cache
> list with the entries. It would not load firmware immediately, instead this
> would trigger a request for the hinted firmware to become available for
> suspend. Then these drivers could request for firmware at resume and it
> will pick up the cached firmware.

I think I am the author the patch [1] mentioned by Marcel. I have to
admit, it's quite
clunky in it's current form.
So yes, the new API you proposed is definitely better to solve the
issue. I'll send
new patch for btusb once we have the new API to use.

Also, with patch [1], the "firmware request while host is not
available" may still get hit
on some corner cases. I proposed another patch [2] to tackle the edge
case, can you
take a look?

[1] https://lkml.org/lkml/2017/8/25/58
[2] https://lkml.org/lkml/2017/8/22/123

Kai-Heng

>
>   Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Back to linux.kernel | Previous | Next | Find similar | Unroll thread

Thread

Re: btusb "firmware request while host is not available" at resume Kai-Heng Feng <kai.heng.feng@canonical.com> - 2017-10-02 10:40 +0200

csiph-web