From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Dmitry Osipenko <digetx@gmail.com>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Chi-hsien Lin <chi-hsien.lin@infineon.com>,
Wright Feng <wright.feng@infineon.com>,
Chung-hsien Hsu <chung-hsien.hsu@infineon.com>,
Kalle Valo <kvalo@codeaurora.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-wireless@vger.kernel.org, Stefan Hansson <newbyte@disroot.org>
Subject: Re: [PATCH v5] brcmfmac: firmware: Fix firmware loading
Date: Mon, 9 Aug 2021 10:23:51 +0200 [thread overview]
Message-ID: <902984be-2c27-e6b0-247b-8d9a94c08cc4@broadcom.com> (raw)
In-Reply-To: <20210808180510.8753-1-digetx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]
On 8/8/2021 8:05 PM, Dmitry Osipenko wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> The patch that would first try the board-specific firmware
> had a bug because the fallback would not be called: the
> asynchronous interface is used meaning request_firmware_nowait()
> returns 0 immediately.
>
> Harden the firmware loading like this:
>
> - If we cannot build an alt_path (like if no board_type is
> specified) just request the first firmware without any
> suffix, like in the past.
>
> - If the lookup of a board specific firmware fails, we get
> a NULL fw in the async callback, so just try again without
> the alt_path from a dedicated brcm_fw_request_done_alt_path
> callback.
>
> - Drop the unnecessary prototype of brcm_fw_request_done.
>
> - Added MODULE_FIRMWARE match for per-board SDIO bins, making
> userspace tools to pull all the relevant firmware files.
The original idea was to setup the path names in
brcmf_fw_alloc_request() function, but with the introduction of the
board_type for NVRAM files that was abandoned and we cook up alternative
paths. Now similar is done for the firmware files. So I would want to
rework the code, but for now I am going with Linus's/Your fix for the
sake of having the regression more or less quickly resolved.
You reported an issue earlier where the firmware callback was called
from the probe context causing it to hang and it is not clear to me
whether that is fixed with this version of the patch.
Regards,
Arend
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2021-08-09 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 18:05 [PATCH v5] brcmfmac: firmware: Fix firmware loading Dmitry Osipenko
2021-08-09 8:23 ` Arend van Spriel [this message]
2021-08-09 14:56 ` Dmitry Osipenko
2021-08-09 15:42 ` Arend van Spriel
2021-08-09 15:58 ` Dmitry Osipenko
2021-08-10 14:15 ` Dmitry Osipenko
2021-08-21 15:46 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=902984be-2c27-e6b0-247b-8d9a94c08cc4@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=chi-hsien.lin@infineon.com \
--cc=chung-hsien.hsu@infineon.com \
--cc=digetx@gmail.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=newbyte@disroot.org \
--cc=wright.feng@infineon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).