Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
	brcm80211-dev-list.pdl@broadcom.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] wifi: brcmfmac: silence warning for non-existent, optional firmware
Date: Sat, 28 Mar 2026 20:18:15 +0100	[thread overview]
Message-ID: <f8eadf0e-6c05-40ed-85fb-316cf4151258@broadcom.com> (raw)
In-Reply-To: <20260317111202.1074675-1-alexander.stein@ew.tq-group.com>

On 17/03/2026 12:12, Alexander Stein wrote:
> The driver tries to load optional firmware files, specific to
> the actual board compatible. These might not exist resulting in a warning
> like this:
> brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4373-sdio.tq,imx93-tqma9352-mba93xxla-mini.bin failed with error -2
> 
> Silence this by using firmware_request_nowait_nowarn() for all firmware
> loads which use brcmf_fw_request_done_alt_path() as callback. This one
> handles optional firmware files.

Thanks, Alexander

I revised the patch hopefully addressing the other firmware related 
warning that Christian Hewitt referred to. I have sent the revised patch 
to the mailing list:

https://lore.kernel.org/linux-wireless/20260328140121.2583606-1-arend.vanspriel@broadcom.com/T/#u

Regards,
Arend

> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
>   .../broadcom/brcm80211/brcmfmac/firmware.c         | 14 ++++++++------
>   1 file changed, 8 insertions(+), 6 deletions(-)

      parent reply	other threads:[~2026-03-28 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 11:12 [PATCH 1/1] wifi: brcmfmac: silence warning for non-existent, optional firmware Alexander Stein
2026-03-18  7:42 ` Christian Hewitt
2026-03-19 11:23   ` Alexander Stein
2026-03-28 19:18 ` Arend van Spriel [this message]

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=f8eadf0e-6c05-40ed-85fb-316cf4151258@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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